Troubleshooting
Problem
Explanation of error, Table with OID ####### was created in a concurrent session, not backed up
Symptom
Example error messages received during a full backup:
[Backup Server] : Backing up Table Constraints
[Backup Server] : Table with OID 1234567 was created in a concurrent session, not backed up.
[Backup Server] : Backing up synonyms [</code>]
Resolving The Problem
The errors mean that tables were created after the backup was started. The next time the backup is run they will be backed up.
When a backup starts, it runs multiple queries to learn about the database schema. In this case, the backup process queried the tables or external tables before it learned about object IDs (OIDs). While the queries ran, an additional table was created. When the backup tried to associate OIDs and table names, the results included a table that was not found in the first query. The backup process could not back up this new table.
If these error messages occur, you may want to stop and then restart the backup to include the newly-created tables. If the newly-created tables are not essential, you can just let the backup run to completion. The next time the backup is run, the newly-created tables will be included in the backup.
Historical Number
NZ995346
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg21572021