DBC:Errors/DBC-E033: Difference between revisions
Jump to navigation
Jump to search
Page 
Created page with "Category:DBCollect {{error|[DBC-E033] <sid>: Instance not available (ORA-???:<Oracle message>)}} The instance <sid> is not in OPEN mode, so {{dbcollect}} cannot connect to it using TNS connection string. The instance may be in MOUNTED mode (Standby database) or in STARTED mode. Solution: * Skip the instance using an <code>N</code> in the 2nd field of the credentials file. * Open the database (if it should be opened) * Run {{dbcollect}} as oracle user without cred..." |
No edit summary |
||
| Line 9: | Line 9: | ||
* Skip the instance using an <code>N</code> in the 2nd field of the credentials file. | * Skip the instance using an <code>N</code> in the 2nd field of the credentials file. | ||
* Open the database (if it should be opened) | * Open the database (if it should be opened) | ||
* Run {{dbcollect}} as oracle user without credentials file (in which case it connects as SYSDBA without requiring a TNS connection | * Run {{dbcollect}} as oracle (or root) user without credentials file (in which case it connects as SYSDBA without requiring a TNS connection | ||
{{PrevNext|DBC:Errors/DBC-E032|DBC:Errors/DBC-E034}} | {{PrevNext|DBC:Errors/DBC-E032|DBC:Errors/DBC-E034}} | ||
Latest revision as of 14:08, 5 November 2024
[DBC-E033] <sid>: Instance not available (ORA-???:<Oracle message>)
The instance <sid> is not in OPEN mode, so dbcollect cannot connect to it using TNS connection string. The instance may be in MOUNTED mode (Standby database) or in STARTED mode.
Solution:
- Skip the instance using an
Nin the 2nd field of the credentials file. - Open the database (if it should be opened)
- Run dbcollect as oracle (or root) user without credentials file (in which case it connects as SYSDBA without requiring a TNS connection
Page