Skip to main content

I was checking the documentation regarding Command Center and SAP For Oracle (brtools).

This leads,for example, to this:

https://documentation.commvault.com/commvault/v11/article?p=112509.htm

This redirects you to the SAP for Oracle documentation, fine: https://documentation.commvault.com/11.21/expert/21968_sap_on_oracle_restores.html

But...the SAP for Oracle documentation only mentions Java console & command line restores/database copy.
Nothing is mentioned regarding the Command Center.
Where is that information?
 

I’m mainly looking for the status of the Oracle in case of a db copy. Should it be stopped/started/mounted/notmounted state, in case of restore (database copy) using the command center.

 

 

 

SAP for Oracle for Command Center is documented in FR 11.22: https://documentation.commvault.com/11.22/essential/131325_performing_sap_for_oracle_database_copy.html

 

For SAP oracle database copies, the destination instance should be in the STARTED state. The restore requirements are the same for both Java GUI and Command center restores. Regarding the documentation part, I will update the thread with more details soon.


--
Mahender

Tnx Mike. I assume it's valid for 11.21 too. ( I didn't check 11.22, because we are not using that one)

@Mahender Reddy ,you say "started",but the docs for 11.22 mentions either mount or nomount.  

 

From oracle, when we put the database in NOMOUNT, in commvault, we will see the status as STARTED.

We say NOMOUNT or MOUNT because we need to know that we can talk to the database with a proper connection string. Once the restore started, the database undergoes multiple restarts until we reach a phase to recreate the control file at the end of the restore.

@Mahender Reddy : do you mean that once it's started,it's enough for CommVault and that he will switch automatically to the correct state?

@Bart : Yes, once we confirm that we can talk to the database in NOMOUNT or MOUNT state with a proper connection, the restore process will switch the database to a required state depending on the restore phase.

Tnx. Maybe it would be a good idea to update the docs, as now it mentions “set the database in the correct state” as prereq, and that actually not needed if the db is started.

Reply


Terms & ConditionsCookie settings