Error upgrading JAVA SP19

[Former Member]

Hello,

I am trying to upgrade to JAVA SP19 and I have the next message when continuing to deploy the components (some of them were deployed previously but I had to do a new deployment due to a Task Limit error):

Caught CVersProxyAccessException while saving repository: CVersAccessException: Can not load mandatory table BC_COMPVERS, desc == null

The last part of the log is:

Jul 29, 2009 2:29:15 PM Info: Ending deployment prerequisites. All items are correct.

Jul 29, 2009 2:29:24 PM Warning: Caught CVersProxyAccessException while saving repository: CVersAccessException: Can not load mandatory table BC_COMPVERS, desc == null

Jul 29, 2009 2:29:24 PM Info: -

---

Ending validation -

---

It is only a Warning, but the error in the JSPM GUI is : "Error during validation of the dependencies of the selected support package stacks"; it say that "You can validate the compoents again by choosing Retry" but after retrying 4 or 5 times it shows the same error.

I set the Database Name to SAP<SID>DB as I saw in other forum threads without success. This does not work.

Thanks in advance for your help.

Raul.

[sunny_pahuja2 · Accepted solution]

Hi Rahul,

It looks like processes and sessions parameter value is less at your database. If sometimes when JSPM tries to load the packages and if value of these parameters are less. then it will show this error.

Check this and change the parameter and restart your database. Then start again.

Thanks

Sunny

[Former Member · Accepted solution]

Hi Sunny,

what are these parameters and what would be these values?

Thanks,

Raúl.

[Former Member · Accepted solution]

Thanks Sunny.

It was very helpful.

Regards,

Raú

[Former Member · Accepted solution]

I am getting a similar error when upgrading from SP18 to SP21. ALL components in the validation phase showed an OK. There was no REVISE for any component. However I am getting an error on the JSPM screen saying validation has failed. In the JSPM logs I see this:

Jan 29, 2010 2:30:01 PM [Error]: ...t.j700.componentvalidator.ComponentValidator.validateAllDependencies(ComponentValidator.java:194) [Thread[main,5,main]]: com.sap.sdt.cvl.provider.api.ComponentProviderException: Cannot read component sap.com/ADSSAP because cannot get access to COMPVERS table

Jan 29, 2010 2:30:01 PM [Error]: com.sap.sdt.jspm.deployment.preparator.QueuePreparator [Thread[main,5,main]]: com.sap.sdt.cvl.provider.api.ComponentProviderException: Cannot read component sap.com/ADSSAP because cannot get access to COMPVERS table

at com.sap.sdt.cvl.provider.impl.CVERSComponentsProvider.loadComponentFromCvers(CVERSComponentsProvider.java:209)

at com.sap.sdt.cvl.provider.impl.CVERSComponentsProvider.hasVersion(CVERSComponentsProvider.java:61)

at com.sap.sdt.cvl.validator.impl.ComponentValidator.validateOwnDependencies(ComponentValidator.java:140)

at com.sap.sdt.cvl.validator.impl.ComponentValidator.validateAllForOwnDependencies(ComponentValidator.java:293)

at com.sap.sdt.cvl.validator.impl.ComponentValidator.validateAllForOwnAndForeignDependencies(ComponentValidator.java:582)

at com.sap.sdt.cvl.validator.impl.ComponentValidator.validateAllForOwnAndForeignDependencies(ComponentValidator.java:574)

at com.sap.sdt.j700.componentvalidator.ComponentValidator.validateAllDependencies(ComponentValidator.java:177)

at com.sap.sdt.j2ee.tools.componentvalidator.AbstractComponentValidator.validateAllDependencies(AbstractComponentValidator.java:138)

at com.sap.sdt.jspm.deployment.preparator.QueuePreparator.checkQueue(QueuePreparator.java:557)

at com.sap.sdt.jspm.deployment.DeploymentFacade.checkQueue(DeploymentFacade.java:366)

at com.sap.sdt.jspm.gui.deployment.CheckQueueStep.prepareUI(CheckQueueStep.java:308)

at com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:359)

at com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:549)

at com.sap.sdt.jspm.phases.PhaseTypeJSPM.execute(PhaseTypeJSPM.java:113)

at com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:738)

at com.sap.sdt.ucp.pce.ctrl.PhaseExecutor.executePhase(PhaseExecutor.java:295)

at com.sap.sdt.ucp.pce.ctrl.PhaseExecutor.execute(PhaseExecutor.java:226)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeClassRef(ActionExecutor.java:204)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:114)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.executeAction(ActionListSequentialExecutor.java:400)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:273)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.doExecute(ActionListSequentialExecutor.java:229)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:152)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeListContainer(ActionExecutor.java:161)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:110)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.executeAction(ActionListSequentialExecutor.java:400)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:273)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.doExecute(ActionListSequentialExecutor.java:229)

at com.sap.sdt.ucp.pce.ctrl.ActionListSequentialExecutor.execute(ActionListSequentialExecutor.java:152)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.executeListContainer(ActionExecutor.java:161)

at com.sap.sdt.ucp.pce.ctrl.ActionExecutor.execute(ActionExecutor.java:110)

at com.sap.sdt.ucp.pce.ctrl.ExecutionDirector.executeAction(ExecutionDirector.java:144)

at com.sap.sdt.ucp.admin.ContextExecutor.executePce(ContextExecutor.java:148)

at com.sap.sdt.ucp.admin.ContextExecutor.execute(ContextExecutor.java:85)

at com.sap.sdt.jspm.main.CmdExecutor.runContext(CmdExecutor.java:127)

at com.sap.sdt.jspm.main.CmdExecutor.executeRun(CmdExecutor.java:100)

at com.sap.sdt.jspm.main.CmdExecutor.execute(CmdExecutor.java:82)

at com.sap.sdt.tools.main.MainProgram.execute(MainProgram.java:479)

at com.sap.sdt.jspm.main.Jspm.main(Jspm.java:195)

Caused by: com.sap.sl.util.cvers.api.CVersAccessException: Error getting connectionjava.sql.SQLException: Listener refused the connection with the following error:

ORA-12519, TNS:no appropriate service handler found

The Connection descriptor used by the client was:

SKNXDSAP01AS:1527:DL0

at com.sap.sl.util.cvers.impl.CVersDao6.findByRealKey(CVersDao6.java:1379)

at com.sap.sl.util.cvers.impl.CVersManager.readCVers(CVersManager.java:395)

at com.sap.sdt.cvl.provider.impl.CVERSComponentsProvider.loadComponentFromCvers(CVERSComponentsProvider.java:195)

... 38 more

Jan 29, 2010 2:30:01 PM [Error]: ...t.j700.componentvalidator.ComponentValidator.validateAllDependencies(ComponentValidator.java:194) [Thread[main,5,main]]: Cannot validate dependencies.

I checked lsnrctl services, and i got a success.

Please let me know if there were any parameter changes that was done to fix your problem.

regards,

Snigdha

[Former Member · Accepted solution]

> what are these parameters and what would be these values?

I ran into the same problem, upgrading from 7.01.4 to 7.01.6. The upgrade worked on standalone sbx and dev systems, but the failed on a clustered QA system.

The jspm_##.trc file at the point where it failed said:

Caused by: com.sap.sl.util.cvers.api.CVersAccessException: readSCVersion1: Listener refused the connection with the following error:

ORA-12519, TNS:no appropriate service handler found

This guy (http://www.atpeaz.com/index.php/2010/fixing-the-ora-12519-tnsno-appropriate-service-handler-found-error/) says to run the command u201Calter system set processes=150 scope=spfile;u201D in the SQL*Plus, and restart the database. It worked!