CTGGF messages

CTGGF0004 Unable to find Oracle home homepath (id homeid).

Explanation

The Oracle Home that was selected for the backup operation was not found on the application server. The IBM Storage Protect Plus catalog or the SLA Policy might contain outdated information about the installed Oracle Homes.

System action

User response

Review the job log and the accompanying application agent logs for more details. Rerun the application inventory job to refresh the catalog.

CTGGF0005 Could not find Oracle database dbname (ID dbid).

Explanation

The database that was selected for the backup operation was not found on the application server.

System action

User response

Review the job log and the accompanying application agent logs for more details. If the database is not running, it must be started and must be in MOUNTED or OPEN mode.

CTGGF0006 No running instance was found for database dbname (ID dbid).

Explanation

The database that was selected for the backup operation was discovered on the application server but no running instance was found for it.

System action

User response

Review the job log and the accompanying application agent logs for more details. If the database is not running, it must be started and must be in MOUNTED or OPEN mode.

CTGGF0031 Database dbname: Backup failed: detailmsg

Explanation

The database failed to backup because one or more errors occurred during the backup process.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0032 Database dbname: Backup failed: detailmsg

Explanation

The database failed to be backed up because an internal error occurred during agent execution.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0038 Database dbname: Failed to mount mountpoint.

Explanation

The log backup operation failed because the log backup target volume could not be mounted. There might be problems connecting to the target storage server.

System action

The log backup operation will be retried on the next scheduled run. If the mount is successful, the next run will back up the logs that were missed by the previous failed run.

User response

Review the job log and the accompanying application agent logs for more details. If the problem occurs frequently, investigate the health of the target vSnap server.

CTGGF0046 Failed to configure log backup schedule for database dbname. Cleaning up.

Explanation

An error occurred while configuring the cron job to schedule the log backup operation.

System action

The partially created cron job, if present, is cleaned up. The cron job configuration will be retried during the next run of the backup job.

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0049 Database dbname: Log backup configuration failed: detailmsg

Explanation

The configuration of the log backup schedule failed for the specified database because one or more errors occurred during the configuration process.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0050 Database dbname: Log backup configuration failed: An internal error occurred.

Explanation

The configuration of the log backup schedule failed for the specified database because an internal error occurred during the agent execution.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0065 Database dbname: Log purge failed: detailmsg

Explanation

An error occurred while trying to delete older, obsolete, archived logs for the specified database.

System action

The log deletion will be retried during the next run of the backup job. Until then, some older archived logs might remain on disk and continue to use up additional space.

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0066 Database dbname: Log purge failed: internal error

Explanation

An error occurred while trying to delete older, obsolete, archived logs for the specified database.

System action

The log deletion will be retried during the next run of the backup job. Until then, some older archived logs might remain on disk and continue to use up additional space.

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0069 Database dbname: Log flush failed: detailmsg

Explanation

An error occurred while trying to back up the latest available archived logs for the specified database.

System action

The restore operation will proceed despite this error. Some logs might be missing during a point-in-time restore. As a result, the database might not be able to be rolled forward to the chosen point in time.

User response

After the restore job is completed, check the status of the restored database and verify that it was successfully restored to the chosen point-in-time. Review the job log and the accompanying application agent logs for more details.

CTGGF0070 Database dbname: Log flush failed: internal error

Explanation

An error occurred while trying to back up the latest available archived logs for the specified database.

System action

The restore operation will proceed despite this error. Some logs might be missing during a point-in-time restore. As a result, the database might not be able to be rolled forward to the chosen point in time.

User response

After the restore job is completed, check the status of the restored database and verify that it was successfully restored to the chosen point-in-time. Review the job log and the accompanying application agent logs for more details.

CTGGF0078 A running instance was not found for database dbname. This error is raised because autostart is enabled in oratab.

Explanation

A database that is listed in oratab is not running even though the autostart flag was set to Y.

System action

User response

The database might be in an invalid state. Investigate the condition of the database, or ignore this message if the database is not critical.

CTGGF0082 The storage layout of datafiles for database dbname cannot be determined.

Explanation

An error occurred while trying to determine the layout of files that are associated with the database. As a result, the database cannot be backed up.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0084 Unable to determine the storage layout of archived logs for database dbname.

Explanation

An error occurred while trying to determine the layout of files that are associated with the database. As a result, the database cannot be backed up.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0088 Unable to collect the Oracle Homes from inventory inventoryfile.

Explanation

An error occurred while trying to collect information about the installed Oracle Homes based on the specified installation inventory file.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0113 Could not find the destination Oracle Home for database dbname.

Explanation

The Oracle Home that was selected as the restore destination was not found on the application server. The IBM Storage Protect Plus catalog might contain outdated information about the installed Oracle Homes.

System action

User response

Review the job log and the accompanying application agent logs for more details. Rerun the application inventory job to refresh the catalog and then define the restore job again.

CTGGF0118 Database dbname: Another database with the same name is already running. The restore operation cannot continue because the overwrite option is disabled.

Explanation

The database cannot be restored while another database with the same name is running.

System action

User response

Select an alternative name for the restored database, or shut down the existing database. Select the overwrite option in the job options to automatically shut down the existing database

CTGGF0121 Database name: Pre-restore validation failed: reason

Explanation

The database cannot be restored because one or more prerequisite checks failed.

System action

User response

Review the job log and the accompanying application agent logs for more details about the failed checks.

CTGGF0122 Database dbname: Pre-restore validation failed: internal error

Explanation

The database cannot be restored because one or more prerequisite checks failed.

System action

User response

Review the job log and the accompanying application agent logs for more details about the failed checks.

CTGGF0156 Database dbname: Restore failed: detailmsg

Explanation

The database failed to be restored because one or more errors occurred during the restore process.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0157 Database dbname: Restore failed due to an internal error.

Explanation

The database failed to be restored because an internal error occurred during the agent execution.

System action

User response

Review the job log and the accompanying application agent logs for more details.

CTGGF0190 Database dbname: No transfer was detected for over timeout seconds. Stopping because the operation appears to have stalled.

Explanation

During an RMAN operation to back up or restore the database, the operation stalled and no data transfer took place during the timeout period.

System action

User response

Review the job log and the accompanying application agent logs for more details. In some cases, this timeout can be an indicator of problems that are caused by stale NFS file handles. You might need to restarted the database.

CTGGF0212 Database dbname: An invalid name was specified for the restored database.

Explanation

The name that was specified for the restored database contains one or more invalid characters.

System action

User response

Specify a valid name for the restored database. The name must begin with an alphabetic character and must consist only of letters, numbers, and the underscore character (_).

CTGGF0214 Database DBname: failed to start the database in mount mode. Error [AttemptNumber] was received.

Explanation

This message is for informational purposes only.

System action

The restore job will fail if this message is issued after the maximum number of attempts is reached.

User response

If the restore fails, search for the error code on the Oracle Knowledge Base and follow the recommended solution. If the error code is ORA-01012, the recovery point might be in a non-recoverable state and another recovery point should be tried. If this issue persists, contact IBM Software Support.

CTGGF0215 Skipping unknown Oracle Home [OraTabHomePath] found in oratab

Explanation

This message is for informational purposes only.

System action

User response

No action is required.

CTGGF0217 Failed to collect log backup diagnostic files for database [DatabaseName] from [JobPath]

Explanation

This message is for informational purposes only.

System action

Diagnostic files from scheduled log backups will not be collected from the Oracle server.

User response

If this issue persists, contact IBM Software Support.

CTGGF0227 /usr/bin/locate not present, cannot search for oratab locations.

Explanation

This message is for informational purposes only.

System action

User response

No action is required.

CTGGF0229 DatabaseName: Errors encountered when shutting down database instance InstName.

Explanation

This message is for informational purposes only.

System action

User response

No action is required.

CTGGF0230 No instances found in srvctl. Instances will be added to srvctl.

Explanation

This message is for informational purposes only.

System action

User response

No action is required.

CTGGF0231 Unexpected line in Oracle DB detail output: Line

Explanation

This message is for informational purposes only.

System action

User response

No action is required.

CTGGF0232 The Oracle version does not support databases in the Oracle home.

Explanation

The Oracle home is running on an unsupported version of Oracle. The version must be Oracle Database 11g Release 2 or later.

System action

Databases in the Oracle home are not protected.

User response

Upgrade to an Oracle version that supports the Oracle home.

CTGGF0237 InstName: Message

Explanation

Output from an Oracle command.

System action

The job might complete as failed or partial.

User response

If the message indicates an error occurred, review the output for information to help resolve the error and apply any suggested fixes.

CTGGF0238 [DbName]: The oradism binary at [OradismPath] is not owned by root.

Explanation

The oradism binary must be owned by root for Direct NFS to function properly.

System action

Test restores fail. Production restores might fail.

User response

Change the owner of the oradism binary in the indicated Oracle Home to root.

CTGGF0239 Oracle homes not found.

Explanation

The Oracle software is installed at the Oracle home. The Oracle agent uses the Oracle Universal Installer metadata to find Oracle homes on the server.

System action

System operation continues, but the Oracle databases on the affected server will not be discovered.

User response

To resolve the issue, complete the following steps:
  • You must review the logs for errors or warning messages
  • You must make sure that the Oracle server is compliant with the IBM Storage Protect Plus Oracle requirements.

CTGGF0240 Oracle databases not found.

Explanation

The Oracle agent discovers the Oracle databases by checking the oratab files and the list of running Oracle processes. If the databases are discovered, the oracle agent attempts to reconcile the databases with the Oracle homes.

The Oracle agent cannot discover the databases due to the following reasons:
  • The Oracle agent does not find a database in the oratab files and the list of running oracle processes
  • The Oracle agent does not reconcile the database with its oracle home.

System action

System operation continues, but the Oracle databases on the affected server will not be discovered.

User response

To resolve the issue, complete the following steps:
  • You must review the logs for errors or warning messages
  • You must make sure theta the Oracle server is compliant with the IBM Storage Protect Plus Oracle requirements.