Check DB finished with warning

Dear all,
Check DB finished with warning from DB13,
kindly check the detail log .
BR0969I Checking database administration...
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342337) 34959360 KB (> 28188060 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342338) 32747520 KB (> 26471824 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342339) 33157120 KB (> 17786284 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342340) 34304000 KB (> 24094204 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 4 files on disk 3342339) 24125440 KB (> 17786284 KB)
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 5 files on disk 3342340) 29286400 KB (> 24094204 KB)
BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPSR3.ZBIMIS
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG1
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCMAP
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG~0
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG1~0
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCMAP~0
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
BR0972I Checking database operations...
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
BR0974I Checking database messages in /oracle/IRP/saptrace/background/alert_IRP.log ...
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
BR0977I Checking database profile...
BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB)
BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
BR0980I Number of changed database profile parameters: 0
BR0280I BRCONNECT time stamp: 2010-03-12 01.04.32
Kindly suggest
Regards

HI
Go to DB20 , Enter the table name ( which are coming in warning) , Press "Refresh" button . You will see
"Old number" and "New Number" are different for those table. Simply click on "Create Statistics" button.
Once you create stats for all the tables shown in warning, run your DB Check job once again.
You have lots of other warning...do some google...you will get most of the information for those warning. Some good links are below
http://download.oracle.com/docs/cd/B12037_01/server.101/b10755/initparams143.htm
http://skywheel.sarang.net/docs/Oracle/10g/server.101/b10755/initparams168.htm
http://youngcow.net/doc/oracle10g/server.102/b14237/initparams209.htm
Regards
Anindya
Edited by: Anindya Bose on Mar 12, 2010 12:35 PM

Similar Messages

Deployment finished with warning when I deploy projects!

Dear All,
I got the error message when I deploy 2 related projects to J2EE, what is the reason? Thanks.
2011-5-27 15:37:57 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[003]Deployment finished with warning
Settings
SDM host : IBM205928
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS1/Temp/temp3258717415907093402cateomp~asc.ear
Result
=> deployment not executed : file:/C:/DOCUME1/ADMINI1/LOCALS1/Temp/temp3258717415907093402cateomp~asc.ear
Unresolved dependencies found for the following SDAs:
1.: development component 'eomp/asc'/'cat'/'CNP_CRMASCTR_D'/'20110527151357'/'0'
dependency:
name: 'eomp/survyapp'
vendor: 'cat'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Deployment exception : Got problems during deployment

Hello
I tried to deploy all components that I can find, but it is still wrong.
Do you know how to check these components which need be deployed? Thanks ...

SAP database check finished with warning

Hello All,
In sapcheck folder latest .chk file finished with following warnings
BR0280I BRCONNECT time stamp: 2009-04-01 10.30.50
BR0972I Checking database operations...
BR0973W Database operation alert - level: WARNING, operation: cdzsjafp.log, time: 2009-01-17 05.13.45, condition: Last 'log' operation failed with rc = 3
Kindly help me resolve the issue.
Regards
Mohsin

>
mohsin m wrote:
> Hello All,
>
> In sapcheck folder latest .chk file finished with following warnings
>
> BR0280I BRCONNECT time stamp: 2009-04-01 10.30.50
> BR0972I Checking database operations...
> BR0973W Database operation alert - level: WARNING, operation: cdzsjafp.log, time: 2009-01-17 05.13.45, condition: Last 'log' operation failed with rc = 3
>
> Kindly help me resolve the issue.
>
> Regards
> Mohsin
Hello,
The warning occurs because the database check looks for the logs of all old operations that ended with an error. The text "Last 'log' operation" means: an operation log with the extension ".log"was found for an action that ended with the (error) status RC = 3.
Since the log referred to is old (January 17), you can get rid of it by running:
brconnect -u / -c force -f cleanup -m 60
(60 is the minimum age of the logs to clean up; adapt this value to your requirements)
Also, it is a good idea to schedule the action "Cleanup logs" periodically via DB13.
Regards,
Mark

DB check finished with warnings CRITICAL_TABLESPACE, object: PSAPSR3USR,

Hello All,
database >> oracle 10g
Autoextend is on for 2 datafile
cd sapcheck >> latest check file finished with warnings
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3USR, value: (max_extn of 2 files on disk 6815746) 36569088 KB (> 32505952 KB)
SQL> select FILE_NAME,BYTES/1024/1024,AUTOEXTENSIBLE,MAXBYTES/1024/1024,INCREMENT_BY from dba_data_files where TABLESPACE_NAME='PSAPSR3USR';
FILE_NAME
BYTES/1024/1024 AUT MAXBYTES/1024/1024 INCREMENT_BY
/oracle/ADE/sapdata1/sr3usr_1/sr3usr.data1
2500 YES 20000 2560
/oracle/ADE/sapdata1/sr3usr_2/sr3usr.data2
2500 YES 20000 2560
kindly help me to resolve issue
Regards
Mohsin
Edited by: mohsin m on Dec 24, 2008 10:59 PM

Hi,
Can you please check the avaliablity of free space on disk.
"CRITICAL_TABLESPACE Warning Description: Examines the data of a tablespace to see whether the file system can be brought to overflow, due to the existing parameter setting (NEXT and MAXSIZE), during the automatic file extension."
--Kishore

DB check finished with warnigs CRITICAL_TABLESPACE, object: PSAPSR3USR

Hello All,
db check finished with warnigs
BR0280I BRCONNECT time stamp: 2008-12-24 10.31.02
BR0969I Checking database administration...
BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3USR, value: (max_extn of 2 files on disk 681
5746) 35840000 KB (> 28193888 KB)
database >>>(oracle 10g)
SQL> select FILE_NAME,BYTES/1024/1024,AUTOEXTENSIBLE,MAXBYTES/1024/1024,INCREMENT_BY from dba_data_files where TABLESPACE_NAME='PSAPSR3USR';
FILE_NAME
BYTES/1024/1024 AUT MAXBYTES/1024/1024 INCREMENT_BY
/oracle/ADE/sapdata1/sr3usr_1/sr3usr.data1
2500 YES 20000 2560
/oracle/ADE/sapdata1/sr3usr_2/sr3usr.data2
2500 YES 20000 2560
Please help me to resolve the issue.
Regards
Mohsin

Hi,
I think u need to check ur size on the disk where the tablespace PSAPSR3USR datafiles are getting stored.
It says that it needs 35840000 KB of disk space but the available disk space available is
only 28193888 KB.
Regards,
Amar.
Edited by: amarnath kurelli on Dec 25, 2008 2:31 PM

DB check finished with warnings

Hello All,
In SAPCHECK latesh .chk file finished with warnings
BR0280I BRCONNECT time stamp: 2009-03-26 10.30.46
BR0815I Number of indexes in schema of owner SAPAUTH: 2
BR0815I Number of indexes in schema of owner SAPR3: 49400
BR0815I Number of indexes in schema of owner SYS: 299
BR0815I Number of indexes/partitions in schema of owner SYSTEM: 228/24
BR0838W Table YSEX_UPL2SAP_1001 not found for segment SAPR3.YSEX_UPL2SAP_1001 - ignoring segment
Kindly help me to resolve the issue.
Regards
Mohsin Mulani

Mohsin,
Please check out following link.
[Re: ORA-03113: end-of-file on communication channel]
Please also check following notes.
Note 1137346 - Oracle Database 10g: Patches for Release 10.2.0.4
Note 871096 - Oracle Database 10g: Patch sets/patches for 10.2.0.
Hope this helps.
Manoj

R3trans check finished with return code:12

Hello!
Can some one help me with the error:
R3trans check finished with return code:12
ERROR: Startup of database failed
/usr/sap/<SID>/SYS/exe/runn/startdb terminating with error 12.
I can start as ora<sid> the oracle, but have problem to start sap.
Thank you very much!
regards
Thom

Dear Thom,
Check ENV variables.Maybe there could be some prob with that .
Please paste the trans.log output of the R3trans -x.
That could help us in suggesting some thing .
Regards
Bharathwaj V

CHECK WRITEABILITY OF BUFFERS finished with return code 12

Hi
When trying to release transports on our Dev system CD1 it takes foreverand a message appear on the bottom of the screen CHECK WRITEABILITY OF
BUFFERS finished with return code 12. Below is a print screen of log file:
1 ETP199X######################################
1 ETP182 CHECK WRITEABILITY OF BUFFERS
1 ETP101 transport order : "CD1K920992"
1 ETP102 system : "CD1"
1 ETP108 tp path : "tp"
1 ETP109 version and release : "372.04.40" "701"
1 ETP198
4 ETP201 Check target systems buffer: "
ctuxdev\sapmnt\trans\buffer\QAS"
3 ETP203 Buffer "
ctuxdev\sapmnt\trans\buffer\QAS" is writeable
2EETP000 The request's target QAS.400 is client dependant but the target
system cannot handle that.
Not sure what the issue is or what has changed as our transport system
has always been working fine.
Regards
Roger

Hi Roger,
I suppose that you are using "Extended Transport Control" in your TMS environmant.
The following link is about the details of "Extended Transport Control":
http://help.sap.com/erp2005_ehp_04/helpdata/EN/1b/9dc2d6e59911d184810000e8a57770/content.htm
To activate "Extended Transport Control", you shoul set tp parameter CTC=1, the default value for it is 0(inactive). At the same time, you should set the value for parameter tp_version to at least 264. For details, please refer to the following link:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/3d/ad5bcf4ebc11d182bf0000e829fbfe/content.htm
->
ctc
Default: 0
Value range: Boolean
ctc stands for Client Transport Control and represents a method of configuration for transport routes. This parameter lets you set specific transport routes using various clients in your system landscape. This method requires an extension of the import buffer. This new format is not understood by old tp programs. Therefore, this new function is switched off by default and the user must explicitly turn it on.
At the same time, the profile generator of the Transport Management System is also delivered. Along with the transport route configuration in the Transport Management System, the transport profile parameter ctc is automatically switched on from the TMS if it is required for your transport landscape.
The new format of the import buffer, activated by ctc=1, requires at least a tp from Release 4.5A. Older tp versions destroy this new import buffer.
When parameter ctc is set, tp requires that you set the value for parameter tp_version to at least 264. This prevents transport control programs with lower version numbers from working with this import buffer. As a result, you can only set the new parameter ctc if all the transport control programs that work with a specific SAP System have at least version 264.
Please check whether ctc=1 and tp_version=264(or higher) are set in transport profile TP_DOMAIN_<SID>.PFL for all systems.
If not, please define them via T-cd:STMS->overview->systems->transport tool.
With Best Regards
Julia Song

Tp finished with return code: 208

Hi Basis Gurus,
I have received transport data and cofiles from system XYZ. I have copied data and cofiles in /usr/sap/trans/data and /usr/sap/trans/cofiles respectively.
Now I have change my directory to /usr/sap/trans/bin
I want to see the Object List before I import the transport request to my test system TST. I have added the transport request XYZK92????? to buffer with tp addtobuffer command and it is successful. Now when I am trying to see the Object list with command tp GETOBJLIST it is giving error message
This is tp version 340.16.12 (release 640)
System XYZ is not defined in TPPARAM
ERROR: System XYZ is not defined in TPPARAM
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
error in transportprofil (param missing, unknown,...)
XYZ system is the system from where I got the transport request and it is not defined in my STMS domain. I guess we can import transport request from any other SAP system.
How to resolve this issue ? is any one aware of this.
Thanks
Best Regards,
CK

I have created the TPPARAM with the above entry. Now getting different error:
~
This is tp version 340.16.12 (release 640)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBLIBPATH is no longer used.
Warning: Parameter DBNAME is no longer used.
Warning: Parameter DBSWPATH is no longer used.
This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).
1AETW065 check-sum error in datafile after "1972" bytes.
2EETW000 Please contact the SAP support.
exiting ...
R3trans finished (0016).
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
WARNS: Highest tp internal warning was: 0101
tp finished with return code: 16
meaning:
A tool used by tp broke down

EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

Hi All ,
 I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
1 . 3 EJB3.0 session DCs
2. 1 JPA DC
I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
--- Deploying file(s):
 D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
--- Status:
 Deploy finished with warnings.
--- Description:
 S U M M A R Y
~~~~~~~~~~~~~~~~~~~
Successfully deployed: 0
Deployed with warnings: 1
Failed deployments: 0
~~~~~~~~~~~~~~~~~~~
1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
 Name:erecapp
 Vendor:asianpaints.com
 Location:J2N_ERECTT_D
 Version:20090217100038
 Deploy status:Warning
 Version:HIGHER
 Description:
 1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
 at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
 at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
 at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
 at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
 at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
 at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
 at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
 at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
 at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
 at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
 at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
 at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

You have to give an explicit data source in your persistence.xml to solve this error normaly.
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
 <persistence-unit name="YOUR_UNIT">
 <jta-data-source>DSNAME</jta-data-source>
Frank

ESS/MSS business packages "Deployed with Warning"

Hello All,
 We are on NW04s SP10 on MS SQL server and Windows server. The Database and portal installations or on different machines. I installed the business packages ESS 1.0, MSS 1.0 and the XSS components - 600 using the JSPM.
After I deploy, I get the message "Deployed with Warning"
When I opened the log files and checked for errors, I found errors in deployment on these SDAs
sap.com/essfiaddr - WEBDYNPRO
sap.com/essinaddr - WEBDYNPRO
sap.com/essinpdata - WEBDYNPRO
sap.com/mssexpdyn - WEBDYNPRO
sap.com/mssexpssa - WEBDYNPRO
sap.com/mssoprogeneraldescription - WEBDYNPRO
And I get the following exceptions for all the SDAs above.
07/01/11 09:54:10 - sap.com/essfiaddr - WEBDYNPRO
07/01/11 09:54:10 - ***********************************************************
Jan 11, 2007 9:54:11 AM Info: End of log messages of the target system.
Jan 11, 2007 9:54:11 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 11, 2007 9:54:11 AM Warning: Finished with warnings: development component 'ess/fi/addr'/'sap.com'/'MAIN_ERP05PAT_C'/'795293':
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/fi/addr and wait.
Reason: Clusterwide exception: server ID 11376250:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/essfiaddr'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/essfiaddr'': The referenced application ''sap.com/ess~per'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
 at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:231)
 at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:317)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
 at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:227)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4684)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4589)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4562)
 at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Now, after this, when I log into the portal and see the MSS role, the links are all missing. I see only Overview and its worksets and pages and Reports and its worksets. Everything else is missing. The warning that I see is "Linked object is unavailable"
Could anyone please suggest me what could be wrong?
Thanks,
Sunitha

Hi Sunitha,
First of all I was not able to find if your backend is ERP 2004 or ERP 2005. It should be ERP 2005 if you want to user ESS 1.0 and MSS 1.0 BP
Please check in Content Administrator if you can locate these applications and test the same. If yes then you can ignore this warning. If No, in that case you have to redeploy XSS, ESS and MSS using SDM again.
The links in portal comes from your backend Area Page Customizing. To verify if the problem is with your Portal Business Package or with your backend customizing run your ESS applications using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTESS
and MSS using
http://<portal>:<port>/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenuArea?sap.xss.menuhdr=SAPDEFAULT&sap.xss.menuargrp=SAPDEFAULTMSS
If you can see all the links correctly here, your backend customization is fine and there is a problem with your BP of ESS and MSS. So you will have to import the same again in the portal. However if you are not able to view the links in the page, then there is a problem with you Area Page Customization. You will need to check your config with the Client 000 configuration to find out the missing config.
Hope this helps.
Regards,
Shubham

Transport Error - tp finished with return code: 152

Howdy All,
I put through some transports into Production on Thursday 22/06/2007 which worked succesfully.
Nothing has changed in the instance profiles, TP Parameters or the TMS. Now when I try to transport a different request I get the following :
26.06.2007                              TP                                     1
Transport executed for:    E75K913986           with command string:
This is E:\usr\sap\P75\SYS\exe\run\tp.EXE version 340.16.31 (release 640)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
The import of the transport request E75K913986 for system P75 was not performed.
Please check the tp command. The buffer entry is printed out below.
P75 buffer:
TASK                .CLI|PROJECT             |P|CMD I |DD Im |Activ |MainI |MC A
---------------+--+--+--
E75K913986          .300|                    | |0000 |      |      |0000 |
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
SWARNS: Highest tp internal severe warning was: 0152
tp finished with return code: 152
meaning:
Nothing done.
Transport function error:    Call failed
E75K913986 has previously been imported. It needs to be re-imported because since it went in another transport (which was created before it) has gone and overwritten some of the objects.
Your advice / guidence would be greatly appreciated, there doesn't seem to be too many articles about this error.
Cheers

I know it has passed 7 years since this problem was recorded, but since we ran into this issue and were looking for assistance, the provided answers above did not apply to our case. Therefore, we add some tips for the readers:
Check the TMS alert in the system where the transpor was created. It can be done in many ways, but you ca do STMS > Monitor > TMS Alert > TMS Alert Viewer
Our issue was with retrofit, which did not exist in 2007. Basically TMS is reporting that the transport of copies that is being expected does not exist, hence "Nothing done".
Solution was to generate in SolMan via report RETRO_SERVICE_CREATE_RFIT_DATA the missing transport of copies. Once that was done, we could perform the transport move.
Regards,
Juan Carlos

Tp finished with return code:8

1.When trying to move a Function Module to higher box..i get an error which says IMPORT failed.
2.The detail description of error is:
Warning : Parameter DBLIBPATH is no longer used.
Warning : Parameter DBSWPATH is no longer used.
tp finished with return code : 8
meaning:
A tool used by tp produced errors.
What could be the possible reason for this error?

Hi,
Did the import fail (got errors) or just got some warnings? Please check the import history of the target system to see if the TR was imported. Did you use CTS (or eCTS) to transport? If so, please check the TMS Configuration for the involved systems. In the Transport Tool tab, verify that you have the correct paths for the DBLIBPATH and DBSWPATH paramters.
Hope it helps.
Regards,
Dao

TP finished with return code : 4

hi
tp import returned with a warning
R3trans.exe finished <0004>.
tp finished with return code : 4
A tool used by tp produced warnings.
What does this warning mean? How to make sure import was fine? (which folders to look for)
Thanks

Hi,
This is very general error that might be because of a number of reasons. You need to check logs of your transport.
Check in /usr/sap/trans/tmp and /usr/sap/trans/log.
Return Code 4 means warning. If it is not critical after checking logs you can also neglect it.
Check this [link|http://help.sap.com/saphelp_nw70/helpdata/en/57/38e26c4eb711d182bf0000e829fbfe/content.htm]
Thanks
Sunny

XML Publisher Report Finished in Warning 11i EBS HRMS

Hi there
I have developed XML Publisher Report using Developer 6i Data Module, this report works fine for specific sets of records. but When I run this report for All Companies This Report Finished in Warning.
Note: XML Data is generated in this report I can see the XML Data in explorer.
This report is for Oracle 11.5.10.2 (HRMS)
Oracle XML Publisher 5.6 Build 45
++++++++++++
AND When I load this XML file into Template at MS Word, I loaded Successfully and When I try to get the PREVIEW, I GET the following ERROR
Font Dir: C:\Program Files\Oracle\XML Publisher Desktop\Template Builder for Word\fonts
Run XDO Start
RTFProcessor setLocale: en-us
FOProcessor setData: M:\ATCO\Disco\Employee Profile Report\Defect\119\XXPEREMPPROFILE4.xml
FOProcessor setLocale: en-us
Regards
ASIM

Is the XML file Complete with all tags closed? Issues with Oracle prevent the completion of the XML file. It truncates in between and hence is not parsed successfully by the XML Template.
Also, try setting the following to 'TRUE' under XML Publisher Administrator>Administration Tab
1) Use XML Publisher's XSLT processor.
2) Enable scalable feature of XSLT processor.
3) Enable XSLT runtime optimization.
Thanks, Naveen Gagadam.

Check DB finished with warning

Similar Messages

Maybe you are looking for