SAP BOXI 3.1 - Error in stdout.log

Hi all,
in the stdout.log file the following error occurs intermittently:
{ERROR} [/OpenDocument].[action] Thread [http-8080-Processor12]; Servlet.service() for servlet action threw exception
java.lang.IllegalStateException
at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:418)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:117)
at com.businessobjects.sdk.credential.WrappedServletResponse.sendError(WrappedServletResponse.java:30)
at com.wedgetail.idm.sso.AbstractAuthenticator.writeAuthenticationChallenge(AbstractAuthenticator.java:1936)
at com.wedgetail.idm.sso.MechChecker.authenticate(MechChecker.java:147)
at com.wedgetail.idm.sso.AbstractAuthenticator.authenticate(AbstractAuthenticator.java:1444)
at com.wedgetail.idm.sso.AbstractAuthenticator.checkAuthenticationOnly(AbstractAuthenticator.java:1330)
at com.wedgetail.idm.sso.AbstractAuthenticator.checkAuthentication(AbstractAuthenticator.java:1139)
at com.wedgetail.idm.sso.AuthFilter.doFilter(AuthFilter.java:148)
at com.businessobjects.sdk.credential.WrappedResponseAuthFilter.doFilter(WrappedResponseAuthFilter.java:66)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.businessobjects.webutil.BrowserRenderingModeFilter.doFilter(BrowserRenderingModeFilter.java:20)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
it happens only when i launch the crystal report instead of the webi report is all good.
We have a SSO Vintela configuration and it works fine.
Recently we notice that the user sessions not release, so we have modified the tomcat configuration for webapps.
We have implemented the note SAP note:
1886165 - How to terminate user
session manually in XI 3.1 and BI 4.0
1286471 - User session not released
for Tomcat in SAP BusinessObjects Enterprise XI 3.x
with success, but the error still remain.
I search in SAP market place but I didn't find anything.
The only doubt is that I've the parameter "logontoken.enabled" set to "false" and I find
this note:
1263840 - OpenDocument Single
sign-on without logon token
But we didn't implement the resolution.
Any one has the same error? Any one has implemented the last note with success?
Let me
know,
Cheers
Paolo

anybody could help me?

Similar Messages

SAP BOXI 3.1 - Error SSO Vintela

In the stdout.log file I received the following error every time I start Tomcat 5.5:
GRAVE: Exception starting filter authFilter
com.wedgetail.idm.sso.ConfigException: No keytab entries for
BOSSO/[email protected]
in "C:\aaaaa.keytab" at
com.wedgetail.idm.sso.util.Util.getKeyTab(Util.java:114)
at
com.wedgetail.idm.sso.AbstractAuthenticator.initAuthenticator(AbstractAuthenticator.java:440)
at com.wedgetail.idm.sso.AuthFilter.init(AuthFilter.java:105)
at com.businessobjects.sdk.credential.WrappedResponseAuthFilter.init(WrappedResponseAuthFilter.java:56)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:223)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:304)
at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:77)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3634)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4217)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
5-mar-2014 16.21.02 org.apache.catalina.core.StandardContext start
GRAVE: Error filterStart
5-mar-2014 16.21.02 org.apache.catalina.core.StandardContext start
GRAVE: Context [/Document] startup failed due to previous errors
In the aaa.keytab with the command klist -target aaa.keytab i don't see the server where the aaa.keytab resides.
If i add the server I resolved the error?
let me know
cheers
Paolo

Hi Seb,
now you suggest me to modify the parameter idm.princ with the value HTTP/<name
of load balancer.XXX.YYY.ZZZ>, add the value -Dcom.wedgetail.idm.sso.password=your_service_account_password
in the java configuration of the two Tomcats.
But the 3rd point? I don't understand why you write Retry by using the FQDN of the LB in the URL.
The value XXX.YYY.ZZZ is my FQDN.
Besides, for the SSO Vintela configuration, i've made changes in web.xml in
the OpenDocument webapps.
One of these changes, it's was to add the following lines:
<init-param>
<param-name>idm.keytab</param-name>
<param-value>C:\WINNT\aaaa.keytab</param-value>
</init-param>
My question is: do i have to comment thaese lines or not?
Regards
Paolo

Error message 'Please log on to the SAP system' when selecting 'shop'

In SRM when we click on 'shop' or 'Goods Receipt' we get the error 'ITS System Information 'Please log on to the SAP System' where it prompts user to log on again. However when user logs on it opens up the same screen again saying please log on to the sap system.
This only happens when we shop using the External ITS (wgate), EBP works fine using the Internal ITS.
Please can someone help.
Kindest Regards
Paul

Hi
Please try this ->
Look using SRM transaction SITSPMON and RZ20, RZ21.
Also Please check SAP OSS Note 517860
-> For ITS, You need to maintain the RFC connection in the connection type "T" i.e TCP/IP. Maintain in the Table - TWPURLSVR.
Ensure that you have maintained correct entries in the TWPURLSVR table using SM30 transaction for the ITS Web path (http or https address path). Note you are passing port - 8001 in the address here. Incase you face problems, Please ask you BASIS person to help you out.
-> Please ask you BASIS person to help you out for maintaining ITS settings. (Ensure IACOR service is running properly - ITS server is running), through the transaction SMICM
-> What all logs appear in SLG1 and SM21 transactions after publishing all the Internet services.
-> If you are using ITS 6.2,you need to do the IACOR settings for SRM on the ITS server.Also in SE80 mainatin the Site for SRM system.After this ,you can publish all the ITS services usig the report,W3_PUBLISH SERVICES.
Related links ->
Integrated ITS :Login Problem
Re: ITS_CANT_LOAD_INCLUDE in BBPstart service
Re: ITS_DEST_NOT_FOUND
Re: ITS Configuration
Re: ITS Template not found
Do let me know.
Regards
- Atul

SAP System Message: Syntx error or generation error in a screen

dear sap basis gurus,
i am currently having problems signing on to our DEV server. i get this error message:
<SID>: SAP System Message
Syntx error or generation error in a screen.
it won't let me log on.
there were no changes made on the server (i.e., profile parameters) lately. it was working really fine after our support package level upgrade about 5 months ago.
have you encountered this problem before? please help me as there we have two imminent go-lives.
thank you very much in advance.
best regards,
albert

hello nick, ashok,
thank you very much for your responses.
i have already resolved this issue by just freeing up some space from our disks. not one of them was full though.
i hope i would no longer encounter the error message.
again, thank you.
best regards,
albert

Error reading job logs of Apps server from Central Instance

Dear Gurus,
We have newly installed system with one CI ( cluster environment) and 2 application Instances.
Systems are recently installed by other team. I am looking into support part after handover.
We have noticed below error while reading failed background job logs from our CI. If suppose any job is failing, we can read respective job log from that application instance but it throws error while reading job log from CI to either of application instance.
I checked /sapmnt/SID/global is shared among all 3 servers and i am successfully able to "Touch a" from applications instances.
Even though i have given "777" permissions to all folders like /sapmnt/SID , /sapmnt/SID/global , /sapmnt/SID/global/400JOB*
I am not able to read job log from CI , for same failed job I can read job log from respective application instance.
Error log :
Error reading job log JOBLGX00080700X39290
Message no. BT167
Diagnosis
The background processing system was unable to read the job log named in the message.
This message suggests that there is a problem with the TEMSE storage system of the SAP system. The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.
This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:
Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
A CRON (or equivalent scheduler) job has deleted the TEMSE file.
The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.
SM21 logs :
Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global
BP_JOBLOG_SHOW: Failed to display jobs. Reason:
> Error reading job log JOBLGX00080700X39290
Strange this is I can check failed job log on one application instance frfom other application instance but not from CI.
Kindly throw some lights where to check.
Regards,

Hi Shravan,
I guess it is related to permission to /sapmnt/SID/global folder. Please ensure owner is sidadm:sapsys in all the systems viz CI, App servers etc.
Check the mounting options are correctly set with read/write mode.
Hope this helps.
Regards,
Deepak Kori

Error in system log

HI all,
this is not a security query, but I need help in this regard.
Following error msg i showing in system log. I'm getting this error whenever i'm trying to read the Job in SM37. And in some cases I'm unable to see the spool list which is generated by the bg jobs. what coul be the reason?
> Error reading job log JOBLGX15165600X64603
Error 2 for write/read access to a file. File = /usr/sap/PRD/SYS/global/999JOBLG/0001X15165600X64603
BP_JOBLOG_SHOW: Failed to display jobs. Reason:

Thanks Jose
Porblem is solved.
/sapmnt/PRD/global and profile are not mounted on that server.
Thnak u so much for ur cooperation.
Regards,
Raja

An error occurred while logging on. (LO 02040)

Hi All;
l get this error when l have connection with liveoffice in xceısus; (but ı can connect with the same parametres of query as a web)
An error occurred while logging on. (LO 02040)
The service cannot be found for the endpoint reference (EPR).
[http://hostname:8080/dswsbobje/services/SLiveOffice]
I get such a error however i couldnt resolve it. Sap Note 1515045 error is all about this but it does not do anything EXCEPT saying uninstall and reinstall it and This is not a solution!!
Is there anyone out there who has exprerienced the same situtation or know how to figure that out?

hi again...
pumpactionshotgun l have already used this service..http://hostname:8080/dswsbobje/services/session
and
Roberto ı use the same connection parts in quaaws and they work if there was a problem about 8080 port it wouldn't work there either..
l have found the solution but thanks for your ideas

DG Observer triggering SIGSEGV Address not mapped to object errors in alert log

Hi,
I've got a Data Guard configuration using two 11.2.0.3 single instance databases. The configuration has been configured for automatic failover and I have an observer running on a separate box.
This fast-start failover configuration has been in place for about a month and in the last week, numerous SEGSEGV (address not mapped to object) errors are reported in the alert log. This is happening quite frequently (every 4/5 minutes or so).
The corresponding trace files show the process triggering the error coming from the observer.
Has anyone experienced this problem? I'm at my wits end trying to figure out how to fix the configuration to eliminate this error.
I must also note that even though this error is occurring a lot, it doesn't seem to be affecting any of the database functionality.
Help?
Thanks in advance.
Beth

Hi.. The following is the alert log message, the traced file generated, and the current values of the data guard configuration. In addition, as part of my research, I attempted to apply patch 12615660 which did not take care of the issue. I also set the inbound_connection_timeout parameter to 0 and that didn't help either. I'm still researching but any pointer in the right direction is very much appreciated.
Error in Alert Log
Thu Apr 09 10:28:59 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc (incident=69298):
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Thu Apr 09 10:29:02 2015
Sweep [inc][69298]: completed
Trace file:
Trace file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning and Oracle Label Security options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1
System name: Linux
Node name: <host name>
Release: 2.6.32-431.17.1.el6.x86_64
Version: #1 SMP Wed May 7 14:14:17 CDT 2014
Machine: x86_64
Instance name: <SID>
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 29902, image: oracle@<host name>
*** 2015-04-09 10:28:59.966
*** SESSION ID:(416.127) 2015-04-09 10:28:59.966
*** CLIENT ID:() 2015-04-09 10:28:59.966
*** SERVICE NAME:(<db_unq_name>) 2015-04-09 10:28:59.966
*** MODULE NAME:(dgmgrl@<observer host> (TNS V1-V3)) 2015-04-09 10:28:59.966
*** ACTION NAME:() 2015-04-09 10:28:59.966
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
DDE: Problem Key 'ORA 7445 [nstimexp()+71]' was flood controlled (0x6) (incident: 69298)
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/cdump'
Data Guard Configuration
DGMGRL> show configuration verbose;
Configuration - dg_config
Protection Mode: MaxPerformance
Databases:
 dbprim - Primary database
 dbstby - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
 FastStartFailoverThreshold = '30'
 OperationTimeout = '30'
 FastStartFailoverLagLimit = '180'
 CommunicationTimeout = '180'
 FastStartFailoverAutoReinstate = 'TRUE'
 FastStartFailoverPmyShutdown = 'TRUE'
 BystandersFollowRoleChange = 'ALL'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: dbstby
Observer: observer_host
Lag Limit: 180 seconds
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Configuration Status:
SUCCESS
DGMGRL> show database verbose dbprim
Database - dbprim
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
 DG_CONFIG
Properties:
 DGConnectIdentifier = 'dbprim'
 ObserverConnectIdentifier = ''
 LogXptMode = 'ASYNC'
 DelayMins = '0'
 Binding = 'optional'
 MaxFailure = '0'
 MaxConnections = '1'
 ReopenSecs = '300'
 NetTimeout = '30'
 RedoCompression = 'DISABLE'
 LogShipping = 'ON'
 PreferredApplyInstance = ''
 ApplyInstanceTimeout = '0'
 ApplyParallel = 'AUTO'
 StandbyFileManagement = 'MANUAL'
 ArchiveLagTarget = '0'
 LogArchiveMaxProcesses = '4'
 LogArchiveMinSucceedDest = '1'
 DbFileNameConvert = ''
 LogFileNameConvert = ''
 FastStartFailoverTarget = 'dbstby'
 InconsistentProperties = '(monitor)'
 InconsistentLogXptProps = '(monitor)'
 SendQEntries = '(monitor)'
 LogXptStatus = '(monitor)'
 RecvQEntries = '(monitor)'
 SidName = ‘<sid>’
 StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
 StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
 AlternateLocation = ''
 LogArchiveTrace = '0'
 LogArchiveFormat = '%t_%s_%r.dbf'
 TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose dbstby
Database - dbstby
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: ON
Instance(s):
 DG_CONFIG
Properties:
 DGConnectIdentifier = 'dbstby'
 ObserverConnectIdentifier = ''
 LogXptMode = 'ASYNC'
 DelayMins = '0'
 Binding = 'optional'
 MaxFailure = '0'
 MaxConnections = '1'
 ReopenSecs = '300'
 NetTimeout = '30'
 RedoCompression = 'DISABLE'
 LogShipping = 'ON'
 PreferredApplyInstance = ''
 ApplyInstanceTimeout = '0'
 ApplyParallel = 'AUTO'
 StandbyFileManagement = 'AUTO'
 ArchiveLagTarget = '0'
 LogArchiveMaxProcesses = '4'
 LogArchiveMinSucceedDest = '1'
 DbFileNameConvert = ''
 LogFileNameConvert = ''
 FastStartFailoverTarget = 'dbprim'
 InconsistentProperties = '(monitor)'
 InconsistentLogXptProps = '(monitor)'
 SendQEntries = '(monitor)'
 LogXptStatus = '(monitor)'
 RecvQEntries = '(monitor)'
 SidName = ‘<sid>’
 StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
 StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
 AlternateLocation = ''
 LogArchiveTrace = '0'
 LogArchiveFormat = '%t_%s_%r.dbf'
 TopWaitEvents = '(monitor)'
Database Status:
SUCCESS

RMAN success, but errors in alert.log file

My RMAN backup script runs well, but generates errors in alert.log file.
Here is the trace file contents:
/usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_3990.trc
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
System name: Linux
Node name: plockton
Release: 2.6.18-128.2.1.el5
Version: #1 SMP Wed Jul 8 11:54:54 EDT 2009
Machine: i686
Instance name: XE
Redo thread mounted by this instance: 1
Oracle process number: 26
Unix process pid: 3990, image: oracle@plockton (TNS V1-V3)
*** 2009-07-23 23:05:01.835
*** ACTION NAME:(0000025 STARTED111) 2009-07-23 23:05:01.823
*** MODULE NAME:(backup full datafile) 2009-07-23 23:05:01.823
*** SERVICE NAME:(SYS$USERS) 2009-07-23 23:05:01.823
*** SESSION ID:(33.154) 2009-07-23 23:05:01.823
*** 2009-07-23 23:05:18.689
*** ACTION NAME:(0000045 STARTED111) 2009-07-23 23:05:18.689
*** MODULE NAME:(backup archivelog) 2009-07-23 23:05:18.689
Does anyone know why? Thanks.
Richard

I'm not sure if this will answer your question or not, but I believe these messages can likely be ignored.
I'm currently running 10.2.0.1.0 Enterprise Edition in pre-production (yes, I know I should apply the latest patchset and I plan to do so as soon as I get a development box allocated to me and can test it's impact). I see the same types of messages that you've reported with each of my regularly-scheduled backups:
a) The alert_<$SID>.log reports that there are errors in trace files:
Mon Aug 10 04:33:49 2009
Starting control autobackup
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Control autobackup written to DISK device
handle '/backup/physical/BLAH/RMAN/cf_c-2740124895-20090810-00'
b) The .trc files, when you look at them contain no errors - only these "informational" messages:
*** 2009-08-10 04:33:50.781
*** ACTION NAME:(0000105 STARTED111) 2009-08-10 04:33:50.754
*** MODULE NAME:(backup archivelog) 2009-08-10 04:33:50.754
*** SERVICE NAME:(SYS$USERS) 2009-08-10 04:33:50.754
*** SESSION ID:(126.28030) 2009-08-10 04:33:50.754
c) I've verified that LOG_ARCHIVE_TRACE is set to 0:
SQL*Plus> show parameter log_archive_trace
NAME TYPE VALUE
log_archive_trace integer 0
As best I can discern from my own experience, these should just be ignored and I trust (read: "hope") they will simply go away once the latest patchset is applied. As for you running Oracle XE, a patchset is not an option, unfortunately.
V/R
-Eric

SAP DEV migration process error

Hi all,
SAP DEV migration process error.Error Details:
Source system
SAP ECC6.0 SR2
DB: DB2.9.1.4
OS: AIX 5.3
Target system
SAP ECC6.0 SR2
DB: DB2.9.1.4
OS: SUSE 10 64 Bit
ERROR 2008-11-13 07:41:06
 CJSlibModule::writeError_impl()
CJS-30023 Process call '/usr/sap/DEV/SYS/exe/run/dipgntab -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits with error code 126. For details see log file(s) dipgntab.log.
TRACE [iaxxejsbas.hpp:460]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2008-11-13 07:41:06 [iaxxgenimp.cpp:731]
 showDialog()
FCO-00011 The step adjustNametab with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_DB6|ind|ind|ind|ind|5|0|adjustNametab was executed with status ERROR .
TRACE [iaxxgenimp.cpp:719]
 showDialog()
<html><head></head><body>An error occurred while processing service SAP ERP 2005 Support Release 2 > Additional Software Life-Cycle Tasks > System Copy > IBM DB2 for Linux, UNIX, and Windows > Target System > Central System > Based on AS ABAP and AS Java > Central System Installation. You may now<ul> <li>press Retry to repeat the current step.</li> <li>press the View Log button to get more information about the error.</li> <li>stop the task and continue with it later.</li></ul>Log files are written to /tmp/sapinst_instdir/ERP/LM/COPY/DB6/SYSTEM/CENTRAL/AS/.</body></html>
TRACE [iaxxgenimp.cpp:1155]
 showDialog()
waiting for an answer from gui
dipgntab.log
/usr/sap/DEV/SYS/exe/run/dipgntab: /usr/sap/DEV/SYS/exe/run/dipgntab: cannot execute binary file

Hi,
1. please check if /usr/sap/DEV/SYS/exe/run/dipgntab exists or not ?
2. Does it have executable permissions?
3. Does your user have authorization to execute it?
4. if you executed dipgntab manually, does it work ?
Regards,
Vincent

Sap Archiving u0096 STO error on version ECC 6.0

Hi experts. I take a long of time with this error and I hope that you can help me. Explain the program.
We have a archiving project of no standard objects. This objects run on Sap version 4.6C, but now, on version ECC 6.0, the Store program give a execution error. The log of the STO Job on Sara transaction is the follow:
Job started
Step 001 started (program RSARCH_STORE_FILE, variant , user ID ARUIZ)
Archive file 000241-001ZIECI_RF02 is being processed
Archive file 000241-001ZIECI_RF02 does not exist (Message no. BA111)
Error occured when checking the stored archive file 000241-001ZIECI_RF02 (Message no. BA194)
Job cancelled after system exception ERROR_MESSAGE (Message no. 00564)
The Write and Delete programs runs correctly.
A strandar Archiving Object like FI_TCJ_DOC runs Ok (WRI, DEL and STO programs). The customazing for both objects are nearly on OAC0, FILE transactions. The changes are on Sap Directories. Write for you the most important customazing actions:
Transaction: FILE
ZIECI_RF02 (No Standard)
Logical File Path --> ZZA_ARCHIVE_GLOBAL_PATH
Physical Path --> /usr/sap/CX6/ADK/files/ZA/<FILENAME>
Logical File Name Definition -->
 ZZA_ARCHIVE_DATA_FILE_ZIECI_RF02
FI_TCJ_DOC (Standard)
Logical File Path --> ARCHIVE_GLOBAL_PATH
Physical Path --> <P=DIR_GLOBAL>/<FILENAME>
Logical File Name Definition --> ARCHIVE_DATA_FILE
Transaction: AOBJ
Customazing settings:
ZIECI_RF02
Logical File Name --> ZZA_ARCHIVE_DATA_FILE_ZIECI_RF02
FI_TCJ_DOC (Standard)
Logical File Name --> ARCHIVE_DATA_FILE
I prove to put in own archiving object (ZIECI_RF02) the logical file name -> ARCHIVE_DATA_FILE too and the error go on.
In the others parameters the values for both objects are:
Delete Jobs: Start Automatically
Content Repository: ZA (Start Automatically)
Sequence: Delete Before Storing
I see the point of the storing STO program (RSARCH_STORE_FILE) where own archiving failed. I made a program with the function and debbuging this can see the next:
REPORT zarm_06_prueba_http_archivado.
DATA: LENGTH TYPE I,
 T_DATA TYPE table of TABL1024.
BREAK ARUIZ.
CALL FUNCTION 'SCMS_HTTP_GET'
EXPORTING
 mandt = '100'
 crep_id = 'ZA'
 doc_id = '47AAF406C02F6C49E1000000805A00A9'
 comp_id = 'data'
 offset = 0
 length = 4096
IMPORTING
 length = length
TABLES
 data = t_data
EXCEPTIONS
 bad_request = 1
 unauthorized = 2
 not_found = 3
 conflict = 4
 internal_server_error = 5
 error_http = 6
 error_url = 7
 error_signature = 8
 OTHERS = 9.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
If execute the program, SAP returns the next error:
Error in HTTP Access: IF_HTTP_CLIENT -> RECEIVE 1
The sy-subrc variable value is 6 -> error_http
The call of the method is the follow:
call method http_client->receive
 exceptions
 http_communication_failure = 1
 http_invalid_state = 2
 others = 3
sy-subrc value is 1 -> http_communication_failure
The unusual of the case are that the Archiving Objects work on SAP 4.6C perfectly,
furthermore on version ECC 6.0 the standard and no standard objects uses Sap Content Server with the same connection (HTTP), IP, PORT and Repository.
I hope that anypeople can help me. A lot of thanks for your time.
Best Regards.

Hi Samanjay.
Answer your questions:
1) I proved the archiving from Sara with the Object ZIECI_RF02 with both customazings. The Stored program fail with logical file name = ZZA_ARCHIVE_DATA_FILE_ZIECI_RF02 and logical file name = ARCHIVE_DATA_FILE (Example at answer 2).
2) AL11 Transaction (Sap Directories):
/usr/sap/CX6/ADK/files/ZA/
cx6adm 09.04.2008 18:02:15 ZIECI_RF02_20080409.180215.ARUIZ
This is the Fich from ZIECI_RF02 on AL11. I prove this yesterday. The variable name: 000241-001ZIECI_RF02 is the generate to save the fich on repository ZA. In this case the variable name is: 000342-001ZIECI_RF02. Can view this with the table ADMI_FILES on TA SE11.
Entries on ADMI_FILES with create date = 09.04.2008
DOCUMENT: 342
ARCHIV KEY: 000342-001ZIECI_RF02
CREAT DATE: 09.04.2008
CREAT TIME : 18:18:28
OBJ COUNT: 1
FILENAME: ZIECI_RF02_20080409.18182
STATUS OPT: Not Stored
STATUS FIL: Archiving Completed
PATHINTERN: ZZA_ARCHIVE_GLOBAL_PATH
CREP:
ARCH DOCID:
Now, I put the same information from FI_TCJ_DOC (Standard Object):
AL11 Transaction (Sap Directories):
/usr/sap/CX6/SYS/global
cx6adm 10.04.2008 11:24:15 FI_FI_TCJ_DOC_20080410_112409_0.ARCHIVE
Entries on ADMI_FILES with create date = 10.04.2008
DOCUMENT: 343
ARCHIV KEY: 000343-001FI_TCJ_DOC
CREAT DATE: 10.04.2008
CREAT TIME: 11:24:09
OBJ COUNT: 2
FILENAME: FI_FI_TCJ_DOC_20080410_112409_0.ARCHI
STATUS OPT: Stored
STATUS FIL: Archiving Completed
PATHINTERN: ARCHIVE_GLOBAL_PATH
CREP: ZA
ARCH DOCID: 47FD890364131EABE1000000805A00A9
Finally, made the example with Archiving Object ZIECI_RF02, but assigning the standard logical file.
AOBJ (Customazing settings):
Object Name: ZIECI_RF02 Archivado de datos: Facturas de Baja
Logical File Name: ARCHIVE_DATA_FILE
Now, execute the archiving at SARA transaction.
AL11 Transaction (Sap Directories):
/usr/sap/CX6/SYS/global
cx6adm 10.04.2008 12:33:25 FI_ZIECI_RF02_20080410_123324_0.ARCHIVE
Entries on ADMI_FILES with create date = 10.04.2008
DOCUMENT: 345
ARCHIV KEY: 000345-001ZIECI_RF02
CREAT DATE: 10.04.2008
CREAT TIME: 12:33:24
OBJ COUNT: 1
FILENAME: FI_ZIECI_RF02_20080410_123324_0.ARCHIVE
STATUS OPT: Not Stored
STATUS FIL: Archiving Completed
PATHINTERN: ARCHIVE_GLOBAL_PATH
CREP:
ARCH DOCID:
It´s that the unusual. At first, I thought that´s the problem was the directory of SAP, but with this proof I looked a new error reason.
3) The details of repository ZA are:
Content Rep: ZA
Description: Document Area
Document Area: Data Archiving
Storage type: HTTP Content Server
Version no: 0046 Content Server version 4.6
HTTP server: 128.90.21.59
Port Number: 1090
HTTP Script: ContentServer/ContentServer.dll
Phys. Path: /usr/sap/CX6/SYS/global/
Too much thanks for your answer and your time. If you have any doubt, question me.
Best regards.

Red box "Write Back Error" OBIEE 11.1.1.6.0

Hi, are there anyone here succeed setup writeback in obiee 11.1.1.6.0 windows or linux system?
I have tried every tutorials on the internet, but always stuck in red box "Write Back Error" and don't have any clue in the log files.
thanks.

hi Devarasu, thanks for reply, I have done all your instruction but still no luck, red box with "write back error" always appear. Do you know how can I track it down? Or should I patch or upgrade to 11.1.1.6.2 BP1 ?

Ecatt error messages in Log while implementing Solution Builder

Hi all,
We are implementing SAP Best Practices using Solution Builder. During the solution builder set up, there is a step where we have to "Upload Installation Data". As per the step, i have downloaded the required BP_CRM_V1_2007_Installation_Data.zip file, unzipped it and uploading it from here. But its resulting in an error, and the log says something about ECATT/BCSET Objects. Has anyone faced a similar problem? Any help would be appreciated. Thank you.
Regards,
Padma Guda

Hi Padma,
could you breif the problem statement?
Regards,
Venky

Error opening installation log file.

ProblemYou are unable to install BlackBerry Desktop Manager and the following error message is displayed when you open the installation log file:
Error opening installation log file verify that the specified log file exist and is writable.
ResolutionTo resolve this issue, edit the system environment variables by completing the following steps:
Warning: The following procedure requires modifying the computer environment variables. This can result in unexpected system behavior. Document the existing values prior to implementing any changes. To search for the Install.log file or files in the temp folder:
On the Start menu, click Run and type %temp%.
Click OK.
In the Temp folder, click Search and then All files and folders. In the All or part of the file name field, type Install.log and set the Look in field value to Temp.
Click Search.
If the Install.log file is found, delete it.
In Windows® Explorer, go to the C:\ drive and create a new folder called TEMP2.
Open the Control Panel and double-click the System icon.
On the Advanced tab, click Environment Variables.
In the User variables list, select TEMP and click Edit.
In the Variable value field, change the file path to C:\TEMP2 and click OK.
In the User variables list, select TMP and click Edit.
In the Variable value field, change the file path to C:\TEMP2 and click OK.
In the Environment Variables window, click OK.
In the System Properties window, click Apply and then OK.
Restart the computer for the changes to take effect.
Repeat the installation procedure for BlackBerry Desktop Manager.
I have 8330

hello,
another solution is here :
http://supportforums.blackberry.com/rim/board/message?board.id=BlackBerryDesktopSoftware&message.id=...
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

Client copy error:cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc

Hi Experts,
While Client copy in Local System , I am facin gthis Error, please anybody help me out.
client copy error:cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc
Regards,
Amit,

Your Error Message is like => cannot open log:/w2k3-web53/sapmnt/trans/log/cc000007.ecc
This means 'w2k3-web53' is your machine name. and your sap system name is 'ECC'.
1) If you are on windows then :
    Type '
w2k3-web53\sapmnt' in address bar, this gives you an error and hence you are getting the above mentioned SAP error.
    Therefore to get out of this error follow the simple steps=>
     I) Create 'sapmnt/trans/log' (recursive) directories anywhere on your machine.
    II) Share 'sapmnt' directory over network {right click on directory->properties->sharing} with full access to others.
   III) Confirm this by typing '
w2k3-web53\sapmnt' in your address bar. 'CC00000*.ECC' will be created automatically by SAP system while copying.
2) If you are using Linux then:
    Create the directories as mentioned above and give full access to directories by using CHMOD command.
    Share 'sapmnt' directory if necessary.
Note: Change the protection level of your client in SAP if necessary:
SCC4->EDIT->Double click your client -> then set Protection level at level 0 {No restriction}.

SAP BOXI 3.1 - Error in stdout.log

Similar Messages

Maybe you are looking for