!!! Oracle FOI server destroyed. !!!
!!! Oracle MapTileServer destroyed. !!!
!!! Oracle Web Map Server destroyed. !!!
Operation Failed: start; OracleInstance: instance1; Component: coreapplication_obis1; msg: 0 of 1 processes started.
Processing Event: SEVERE: Element Type: PROCESS, Element Id: instance1:coreapplication_obis1, Operation Result: FAILED_TO_START, Detail Message: Operation Failed: start; OracleInstance: instance1; Component: coreapplication_obis1; msg: 0 of 1 processes started.
Odbc driver returned an error (SQLDriverConnectW)
Unable to create a system user connection to BI Server during start up. Trying again.
As evident from error list, the issue was somewhere in connection pool, and sure enough, we had incorrect connection type (also reffered to Call Type). I changed it from ODBC 3.5 to OCI 10g/11g and saved the RPD. This made the services to start properly with no issues.
This can be confusing, as settings on client machine for connecting to database can be different than settings on the server. However when publishing the RPD, settings must be those applicable for server.
All well, except one problem, the report still gave TNS error (Unable to connect to database). For this, we had to change the user ID used in RPD, that had access to tables, and also check 'Require Fully Qualified Table Names' within the connection pool settings. This made the error disappear
No comments:
Post a Comment