Hi All,
We are facing issues while publishing the Universe onto the repository. Just to give a background of the issue, we are connecting to Oracle 9i database from BO 4.1 SP4 Information Design Tool. We have client tools installed on one VM server and BO enterprise server on the other VM . I have installed Oracle 11g client 32 bit on the client tools server and 64 bit on BO Enterprise server. I can create a session to the BO server from the IDT tool successfully I have even created a secured connection published on SAP BO server which means there are no port issues.
I create the data foundation and business layer on IDT. I have created a test one with only two simple tables and do an integrity check and it works fine. When I publish the Universe, after I click the Finish button, it just freezes and doesnt get anything back for a long time. After that period, the finish button gets enabled again and if I check on the server, Universe is not published.
Based on the KB 1586166 - How to enable tracing for BI4.x client applications I created two BO_Trace.ini file in the following directories:
C:\<user-dir>\.businessobjects\bimodeler_14\config
D:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf
I was getting the trace files earlier as well but I just changed to see if something happens. I I have a hs_error_pid4198 file created on monday, but it seems to be a java environment error file. I am not sure if its related. The trace I see on the InformationDesignTool_ncs file is
---------------------------------------------------
trc file: "InformationDesignTool_ncs.trc", trc level: 1, release: "720"
---------------------------------------------------
M
M [Thr 5788] Thu Aug 21 11:09:28 2014
M [Thr 5788] NCS trace timer thread is successfully triggered
M [Thr 5788] Trace dispatcher thread is successfully triggered
M [Thr 5788] NCS data timer thread is successfully triggered
M [Thr 5788] Data dispatcher thread is successfully triggered
M [Thr 5788] NCS library version 2.3.9 (unicode) loaded
M [Thr 5788] NCS_ProcInit API invoked
M
M [Thr 5052] Thu Aug 21 11:09:33 2014
M [Thr 5052] ***LOG Q0I=> NiBufIConnect: connection pending after 500ms: connect (10035: WSAEWOULDBLOCK: Resource temporarily unavailable) [nibuf.cpp 4634]
M [Thr 5052] *** ERROR => NiBufIConnect: non-buffered connect pending after 500ms (hdl 1;127.0.0.1:59818) [nibuf.cpp 4645]
M [Thr 5052] *** ERROR => NI raw handle failed to be initilized at IDEL to CONNECTED, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 137]
M
M [Thr 5740] Thu Aug 21 11:10:28 2014
M [Thr 5740] *** ERROR => NI raw handle failed to be initilized at IDEL to CONNECTED, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 137]
M
M [Thr 2428] Thu Aug 21 11:53:19 2014
M [Thr 2428] NCS_ProcExit API started
M
M [Thr 2428] Thu Aug 21 11:53:20 2014
M [Thr 2428] Timer threads are successfully finished
M [Thr 2428] Data sending threads are successfully finished
M
M [Thr 2428] Thu Aug 21 11:53:21 2014
M [Thr 2428] NCS_ProcExit API invoked
Initially I was getting the following error on 18 Aug 14
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
ENCODING:UTF-8
RECORD_SEPARATOR:30
COLUMN_SEPARATOR:124
ESC_CHARACTER:27
COLUMNS:Location|Guid|Time|Tzone|Trace|Log|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text
SEVERITY_MAP: |None| |Success|W|Warning|E|Error|A|Assertion
HEADER_END
|3E293DA41362474BA0789573468E97B20|2014 08 18 16:44:52.105|+1000|Error| |>>|E| |idt| 4168| 1|main | ||||||||||||||||||||||Cannot read TraceLog configuration file 'conf/tracelog.ini'.-
|3E293DA41362474BA0789573468E97B21|2014 08 18 16:46:02.808|+1000|Error| |==|E| |idt| 4168| 40|Check integrity CIR 01401| ||||||||||||||||||||com.businessobjects.mds.services.parser.decoder.DataFoundationSQLDecoder||DataFoundationSQLDecoder.decodeExpression: encodedExpression is null-
I am not seeing this error after I created the tracelog file .ini based on the KB mentioned. I have a trace file generated in the workspace folder but its 12MB size which I wont be able to post it here.
Any suggestions to resolve this error would be of great help.
Regards,
Rohini.