Question Re: BI-BO various Logging errors after Internal error during installation in Technology Q&A

BI-BO various Logging errors after Internal error during installation

former_member341172 — Thu, 11 Jan 2018 10:52:25 GMT

Hi,

I wanted to share with an unsual situation where I have got an "Internal Error" during the BO installation and ask for the solutions to the errors I have noticed in the BO logging after the Repair of BO installation. The installation have been done to add/install the CMS Drivers using Modify (./modifyOrRemoveProducts.sh) using the initial SAP BO installation. During the installation the error poped up and I needed to "Repair" the initial BO istalltion.

Everything, excep the dynamic recipients for Publications seems to work fine from the user perspective. However, I have noticed many new errors in the logging directory. Can you help me find the sollutions to the errors I still have not solved? The errors are taken from the logs in sap_bobj/logging directory for both .glf and .log type of logs.

Log Error 2 - Monitoring (appears very often, even when no user activity)

unable to close the iterator -1: com.businessobjects.cdz_ext.ExtensionManagementException : iterator (id=-1) not found : it has been closed or never created (major=0, minor=0)
Error caught during monitoring
at com.businessobjects.ds.excel.corba.ExcelDataSourceServant.convertException(Unknown Source)
<...> (Unknown Source)
at com.businessobjects.cdz_ext.lifecycle.MonitoringThread.run(Unknown Source)

Log Error 3 - isBag

isBag called on null property
Unknown property type
isBag called on null property
Unknown property type

Log Error 4 - Oracle OCI

Oracle OCI|Oracle 11|JobId:603983600|ENTER OCIErrorGet  
<…>
Oracle OCI|Oracle 11|JobId:603983600|EXIT OCIErrorGet with return code 0 (OCI_SUCCESS)  
OraText * 0x0x7fe35b50bb90 [ORA-24347: Warning of a NULL column in an aggregate function
Oracle OCI|Oracle 11|JobId:603983600|ENTER OCIErrorGet  
<…>
Oracle OCI|Oracle 11|JobId:603983600|EXIT OCIErrorGet with return code 100 (OCI_NO_DATA)  
<…>  
OraText * 0x0x7fe35b50bb90 [ORA-24347: Warning of a NULL column in an aggregate function

Log Error 5 - Report not found (running schedule)

**ERROR:C3_QFDocument:Report not found [kc3qfdocument.cpp;2178]
Failed to get session id from handle and handle is not set to bypass nor server-server discovery

Log Error 6 - Default Limits can't be changed

**ERROR:C3_DS:(A) *** Default Limits can't be changed *** : (MxRows == ULONG_MAX && MxTime == ULONG_MAX && WarnTime == ULONG_MAX) [kc3cdbds.cpp;1272]

Log Error 7 - Obj key not found

**ERROR:C3_QFReportPart:Obj key not found : LD [kc3UserReportPart.cpp;1143]
**ERROR:C3_QFReportPart:UIREF malformed : UIREF:V= <...>

Log Error 8 - GenericParser

|**ERROR:C3_GenericParser:ValueTypedConstant::Validate
- Client - Invalid value : 5.561e3 [kc3xmlGenericParser.cpp;246]

Log Error 9 - CalculatorCtxt

**ERROR:C3_CalculatorCtxt:(A) cannot find nm to check IsDependOnSMWithEvalError() : (false) [kc3cdbCtxt.cpp;6006]

Log Error 10 - Duplicate object

**ERROR:TRACE_MODULE_NAME:Duplicate object found in document objects : DP1.DO965 [kc3cdblocalds.cpp;227]

Log Error 11 - Unable to get comments

**ERROR:repeng:Unable to get comments from database :Infoobject with cuid:olX6emEAAIEqdDQAZQ_E._oFggw not found(possibly no rights) with error code:CMNTRY 002 [kreCommentManager.cpp;174

(not related with the installation)

Log Error 13 - GC (Allocation Failure) Garbage Collection.

[GC (Metadata GC Threshold) [GC (Allocation Failure)
[PSYoungGen: 257024K->23008K(519168K)] 285215K->51200K(868864K), 0.0468420 secs] [Times: user=0.09 sys=0.01, real=0.05 secs]
https://blogs.sap.com/2017/03/18/an-small-example-to-learn-garbage-collection-in-java-and-in-abap/
I have added more memorry to the Tomcat (4GB) but I am still getting those failures.

Re: BI-BO various Logging errors after Internal error during installation

denis_konovalov — Thu, 11 Jan 2018 13:02:49 GMT

There are errors you list which can't be possibly related to the install errors you listed.
Like Oracle or GC (garbage collection errors in /logging directory have nothing to do with tomcat - they are from either processing or APS/AJS servers.
If you believe that error started after you modified install - start investigating what happened during that process.
Review installData/logs setupengine.log from that process - see if anything interesting happened.

p.s.
mentioning your version/product and architecture would be nice too.

Re: BI-BO various Logging errors after Internal error during installation

former_member341172 — Fri, 12 Jan 2018 12:23:51 GMT

Current versions: SAP BO 4.2 SP04 Patch 04 (initial install SAP BO 4.2 SP2) + SAP Lumira server for BI Platform 1.31 patch 8.

OS: Red Hat Enterprise Linux Server release 6.8 (Santiago)

After the error during the modify installation I have run the repair - it went fine without any errors.

Have not checked the history logs of GC - it might be that this is an old issue. However, the other errors appeared the next day after the installation - including the Oracle OCI. It might be because Oracle DB was a source for a scheduled report. However it used to work fine before. Will try to check the Audit what is happening when the Oracle error appears.

Setup Error Log (when running Modify):

ErrorsAndWarnings.log
Error: Error in SqliteTable::ExecQuery(): 
Error:  Statement: RELEASE UpdateDUPropertiesError:  
Error:  database is lockedError: Exception thrown while accessing manifest (caught ManifestAccessException) : 
Error: Internal error detected. Program will exit

SetupEngine.log
Adding property: tp.sap.introscope.props-822-core$introscope_ent_instrumentation. Value: false
[INSTALL] DUMapIndex::getDUByName refId: tp.sap.introscope.props-822-core, COMS: nu, DOMS: 32
[INSTALL] DUMapIndex::getDUByName refId: tp.sap.introscope.props-822-core, COMS: nu, DOMS: 64
[INSTALL] DUMapIndex::getDUByName refId: tp.sap.introscope.props-822-core, COMS: nu, DOMS: nu
Adding property: tp.sap.introscope.props-822-core$introscope_ent_port. Value: 6001
Error: Error in SqliteTable::ExecQuery(): 
Error: Statement: RELEASE UpdateDUProperties
Error: Error: database is lockedPerlUIProgressMonitor::done()
Error: Exception thrown while accessing manifest (caught ManifestAccessException) : 
Error: Statement: RELEASE UpdateDUPropertiesError: Error: 
Error: Note that even though the program has terminated abnormally, the manifest should not be left in a corrupt state.
Error: Internal error detected. Program will exit.PerlUISession::ShowMessage() called.

Re: BI-BO various Logging errors after Internal error during installation

denis_konovalov — Fri, 12 Jan 2018 13:38:39 GMT

I think you should open a support incident with SAP to properly review this.
Posting errors on their own is not going to be productive.
First one could point to your sqllite manifest file being corrupted and second one points to same...

Make sure you use KBA 1681036 to generate survey script when opening SAP Incident with BI-BIP-INS component to review issue with Upgrade/Modify process.
Still not convinced the other errors you shown are related.

Re: BI-BO various Logging errors after Internal error during installation

Former Member — Wed, 27 Feb 2019 09:20:36 GMT

Hi @Vytautas were you able to get this resolved? We have a similar problem and would like to know what your solution is?

Thanks