Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O Database Migration Service usa o Cloud Logging. Você pode acessar duas categorias de registros para
adquirir informações detalhadas sobre eventos relacionados aos seus jobs
de migração: registros do Database Migration Service e registros do AlloyDB para PostgreSQL de destino.
Cada entrada de registro contém um campo jsonPayload.textMessage com uma descrição para ajudar você a entender melhor o evento. Há diferentes tipos de mensagens, por exemplo:
Exemplo de mensagens de registro para o recurso datamigration.googleapis.com/MigrationJob
Mensagem de texto de registro
Descrição
FULL DUMP read is completed for table: {SCHEMA_TABLE_NAME}
Essa mensagem significa que o Database Migration Service terminou de ler
dados específicos da tabela no banco de dados de origem para a fase de despejo completo.
Essa mensagem indica que a fase de despejo completo da tabela está
em um estágio avançado e provavelmente será concluída em breve.
Successfully loaded {NUMBER} FULL DUMP rows into table: {SCHEMA_TABLE_NAME}
Essa mensagem significa que o Database Migration Service terminou de gravar um lote de linhas em uma tabela específica no cluster de destino durante a fase de despejo completo.
Successfully applied {NUMBER} CDC rows into table: {SCHEMA_TABLE_NAME}
Essa mensagem significa que o Database Migration Service terminou de gravar um lote de
linhas em uma tabela específica no cluster de destino durante a fase de CDC.
Accessing data of table: {SCHEMA_TABLE_NAME} for data processing purpose
Quando você
usa uma CMEK
no job de migração, essa mensagem indica que
o Database Migration Service acessou a chave de criptografia para processar dados
de uma tabela específica.
Na guia Jobs, clique no nome de exibição do job de migração
para o qual você quer ver os registros.
A página de detalhes do job de migração é aberta.
Na página de detalhes do job de migração, clique em Ver registros e faça uma
das seguintes ações:
Para ver os registros de jobs de migração, selecione Registros de jobs de migração.
Para ver os registros do cluster de destino do AlloyDB para PostgreSQL, selecione Registros da instância de destino.
A página Análise de registros é aberta.
Na página Análise de registros, use os menus suspensos
para modificar a consulta e filtrar as entradas de registro. Por exemplo, para filtrar os registros de jobs de migração de eventos em que o Database Migration Service acessou uma tabela específica no banco de dados de origem, use uma consulta semelhante a esta:
resource.type="datamigration.googleapis.com/MigrationJob"
resource.labels.migration_job_id="MIGRATION_JOB_ID"
jsonPayload.textMessage:"Accessing data of table"
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-05 UTC."],[[["\u003cp\u003eDatabase Migration Service uses Cloud Logging to provide detailed information on migration job events, accessible through two log categories: Database Migration Service logs and destination AlloyDB for PostgreSQL logs.\u003c/p\u003e\n"],["\u003cp\u003eDatabase Migration Service logs offer structured logs for \u003ccode\u003eMigrationJob\u003c/code\u003e and \u003ccode\u003eConnectionProfile\u003c/code\u003e resources, capturing real-world events like job creation, source database data reading, and connection profile edits.\u003c/p\u003e\n"],["\u003cp\u003eEach log entry in the Database Migration Service logs includes a \u003ccode\u003ejsonPayload.textMessage\u003c/code\u003e field that describes the event, such as completion of a table's full dump read, successful loading of rows, or accessing data for processing.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB for PostgreSQL also provides log entries for the destination cluster, which are detailed in the Cloud Logging documentation under the AlloyDB for PostgreSQL logs reference.\u003c/p\u003e\n"],["\u003cp\u003eThe Logs Explorer in the Google Cloud console enables users to view and filter logs by specific criteria, such as migration job ID and message content, to track events like Database Migration Service accessing data of a specific table.\u003c/p\u003e\n"]]],[],null,["# Logging\n\nDatabase Migration Service uses Cloud Logging. You can access two log categories to\nacquire detailed information on events that occur with relation to your migration\njobs: Database Migration Service logs, and the destination AlloyDB for PostgreSQL logs.\n\nDatabase Migration Service logs\n-------------------------------\n\nDatabase Migration Service for Oracle to AlloyDB for PostgreSQL provides\n[structured logs](/logging/docs/structured-logging#structured_logging_special_fields) for the\n[`datamigration.googleapis.com/MigrationJob`](/database-migration/docs/reference/rest/v1/projects.locations.migrationJobs#resource:-migrationjob),\n[`datamigration.googleapis.com/ConnectionProfile`](/database-migration/docs/reference/rest/v1/projects.locations.connectionProfiles),\nand\n[`datamigration.googleapis.com/PrivateConnection`](/database-migration/docs/reference/rest/v1/projects.locations.privateConnections)\nresources.\nThese logs represent real-world events, such as when a migration job is created,\nwhen Database Migration Service reads information from your source database,\nor when a connection profile is edited.\n\nEach log entry contains a `jsonPayload.textMessage` field with a description to\nhelp you better understand the event. There are different types of messages,\nfor example:\n\nAlloyDB for PostgreSQL cluster logs\n-----------------------------------\n\nAlloyDB for PostgreSQL also provides log entries for your destination cluster.\nSee the\n[AlloyDB for PostgreSQL logs reference](/logging/docs/api/platform-logs#alloydb) in the Cloud Logging documentation.\n\nView and query logs\n-------------------\n\nTo view your logs, perform the following:\n\n1. In the Google Cloud console, go to the **Migration jobs** page.\n\n [Go to Migration jobs](https://console.cloud.google.com/dbmigration/migrations)\n2. In the **Jobs** tab, click the display name of the migration job for which you want to view logs.\n\n The migration job details page opens.\n3. On the migration job details page, click **View logs** and perform one of the following:\n - To view migration job logs, select **Migration job logs**.\n - To view logs for your AlloyDB for PostgreSQL destination cluster, select **Destination instance logs**.\n\n The **Logs Explorer** page opens.\n4. On the **Logs Explorer** page, you can use the drop-down menus to modify the query and filter log entries. For example, to filter migration job logs for events where Database Migration Service accessed a specific table in your source database, you can use a query similar to the following: \n\n ```bash\n resource.type=\"datamigration.googleapis.com/MigrationJob\"\n resource.labels.migration_job_id=\"\u003cvar translate=\"no\"\u003eMIGRATION_JOB_ID\u003c/var\u003e\"\n jsonPayload.textMessage:\"Accessing data of table\"\n ```\n\nWhat's next\n-----------\n\n- For more information on using Logs Explorer, see\n [View logs by using Logs Explorer](/logging/docs/view/logs-explorer-interface).\n\n- For a detailed reference of what fields are supported in Database Migration Service\n log entries, see\n [Database Migration Service logs reference](/logging/docs/api/platform-logs#cloud_database_migration_service).\n\n- To get a complete, step-by-step migration walkthrough, see\n [Oracle to AlloyDB for PostgreSQL migration guide](/database-migration/docs/oracle-to-alloydb/guide)."]]
