Applying Patch 20692324: PLMMOBILE3.1 to Managed Server Causes java.io.FileNotFoundException Error and Cannot Start the Managed Server (Doc ID 2086425.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Product Lifecycle Management Mobile - Version 3.1 and later
Oracle Agile PLM Framework - Version 9.3.3.0 and later
Information in this document applies to any platform.

Symptoms

Applying <Patch 20692324>: PLMMOBILE3.1 to managed server causes java.io.FileNotFoundException error and cannot start the managed server.

This issue occurs on the following conditions:

  1. Operating System where the managed server is installed is non-english Operating System.
  2. Clustered Instance. For example, Server 1 have Admin server and Managed server installed and Server 2 have Managed server installed. Issue is happening in Managed Server on Server 2. For Server 1 Admin server and managed server, it can start without any issues.

Below error can be observed in stderr.log on Server 2 managed server.

Error
java.io.FileNotFoundException: C:\Agile\Agile933\agileDomain\config\log.xml.12-04-2015_03.44.41-?? (ファイル名、ディレクトリ名、またはボリューム ラベルの構文が間違っています。)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.copy(DataUpdate.java:265)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.copyOrExtractTo(DataUpdate.java:202)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.updateLocalData(DataUpdate.java:168)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.doUpdate(DataUpdate.java:299)
at weblogic.deploy.internal.targetserver.datamanagement.ConfigDataUpdate.doUpdate(ConfigDataUpdate.java:112)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.update(DataUpdate.java:72)
at weblogic.deploy.internal.targetserver.datamanagement.Data.commitDataUpdate(Data.java:118)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateFiles(RuntimeAccessDeploymentReceiverService.java:921)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleRegistrationResponse(RuntimeAccessDeploymentReceiverService.java:769)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.registerHandler(RuntimeAccessDeploymentReceiverService.java:740)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.start(RuntimeAccessDeploymentReceiverService.java:179)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:883)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:570)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:74)


Steps

  1. On Server 1 where admin server and managed server is installed, apply <Patch 20692324> and perform the steps mentioned in the patch readme.
  2. On Server 2 where managed server is installed, apply <Patch 20692324> and perform the steps mentioned in the patch readme.
  3. On Server 1, start the admin server and managed server
  4. On Server 2, start the managed server

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms