Common error messages when installing Infrastructure Management with Oracle as  the database


This topic lists the common error messages recorded in oracleDBAIface.log, pronet_db.log, and tsim_server_install_log.txt log files when installing TrueSight Infrastructure Management with Oracle as the database.

Error messages

Error scenario

Error seen in oracleDBAIface.log and tsim_server_install_log.txt

Wrong port number

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [Io exception: The Network Adapter could not establish the connection]

Wrong but valid host name (The host does not have Oracle installed)

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [Io exception: The Network Adapter could not establish the connection]

Wrong SID

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details: [Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: <client name: descriptor> ]

Wrong DBA password

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [ ORA-01017: invalid username/password; logon denied ]

Wrong DBA user name

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [ORA-01017: invalid username/password; logon denied ]

Wrong data file path

Error with provided datafile: ORA-01119: error in creating database file '<root directory>:\app\Administrator\oradata\orcl1\main19mar.dbf' ORA-27040: file create error, unable to create file OSD-04002: unable to open file O/S-Error: (OS 3) The system cannot find the path specified.

Not enough space on the Oracle server

Run with Output- ORA-01119: error in creating database file '<root directory>:\app\Administrator\oradata\ora112db\MAIN3201.DBF'
ORA-27044: unable to write the header block of file
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 112) There is not enough space on the disk.
and return code 1]}

Listener is not running

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [Io exception: The Network Adapter could not establish the connection]

Instance parameter value does not match for: process

The parameter [processes] is set lower than expected value. It is set to [500]. Expected value is [1000].

Instance parameter value does not match for: job_queue_processes

The parameter [job_queue_processes] is set lower than expected value. It is set to [0]. Expected value is [20].

Instance parameter value does not match for: parallel_execution_message_size

Detail=[The parameter [parallel_execution_message_size] is set lower than expected value. It is set to [2148]. Expected value is [4096].

Data file name is not provided, but path is provided

Error with provided datafile: ORA-01119: error in creating database file '<root directory>:\app' ORA-27038: created file already exists
process
OSD-04010: <create> option specified, file already exists

TrueSight Infrastructure Management installation tables exist in the Oracle instance

Description=[Unable to validate the Oracle DB configuration details for creation of tablespace and user settings ],Detail=[There is one more oracle user [PROACT409] having bppm schema on the same oracle sid/service.]\}

Oracle instance is down

Unable to connect to Oracle database with given credentials. The computer must have SYSDBA privileges. Details [Listener refused the connection with the following error:ORA-12505, TNS:listener does not currently know of SID given in connect descriptor. The Connection descriptor used by the client was: <connection descriptor>]

Insufficient privileges

When you install or upgrade the TrueSight Infrastructure Management Server with Oracle as a database, an ORA-01031: insufficient privileges error message might be displayed in the pronet_db.log file. You can ignore this message.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*