Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

latest opatchauto apply failed when runs in AEST timezone (Australian eastern time)

edited Jan 10, 2017 7:10PM in Database Install/Upgrade/Opatch (MOSC) 2 commentsAnswered

Hello experts,

[oracle@localhost OPatch]$ ./opatchauto version

Oracle OPatchAuto Version 13.9.0.1.0

Copyright (c) 2016, Oracle Corporation.  All rights reserved.

1. OPatchAuto version 13.9.0.1.0

2. OpatchautoDB version 12.2.0.1.5

Opatch 12.2.0.1.5 , use opatchauto apply patch 22378102. Timezone $TZ of root and oracle is  Australia/Sydney which is AEST. At the last step of opatchauto, it involves 'opatch lsinv' to check if the patch has been applied, anyway this step failed. If manually run opatch lsinv, it failed either with error 'java.text.ParseException: Unparseable date: "2016.Jul.18 16:30:01 AEST"'. The problem is that default java in oracle home doesn't support AEST.


I only have single instance db in AEST server, so I did test with opatch, anyway similar result.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center