Rene,
I don't think it is installed/configured.
$gpnptool get
Warning: some command line parameters were defaulted. Resulting command
line:
$GI_HOME/bin/gpnptool.bin get -o-
Fatal error: cannot get local GPnP security keys (wallet).
Fatal error: cannot initialize GPnP, CLSGPNP_ERR (Generic GPnP error).
Fatal: GPnP init failed. Make sure GPnP client setup is correct (wallets,
etc.)
Thank you,
Chen
On Tue, Jun 14, 2016 at 10:46 AM, Rene Antunez <grantunez@xxxxxxxxx> wrote:
Use *gpnptool get* to get the GPnP profile
Regards
René
On Tuesday, June 14, 2016 12:42 PM, Chen Zhou <oracle.unknowns@xxxxxxxxx>
wrote:
Sumit,
There is no file in my $GRID_HOME/gpnp/<hostname>/profiles/peer
directory. It is the same for other 11.2.0.4 database servers.
Thank you,
Chen
On Tue, Jun 14, 2016 at 4:14 AM, sumit Tyagi <dba.tyagisumit@xxxxxxxxx>
wrote:
Please check the ASM_DISKSTRING value in GPNP profile .
The GPnP profile is a small XML file located in
$GRID_HOME/gpnp/<hostname>/profiles/peer under the name profile.xml.
On Mon, Jun 13, 2016 at 11:15 PM, Chen Zhou <oracle.unknowns@xxxxxxxxx>
wrote:
Hi, Everyone,
This is a stand-alone 11.2.0.4 EE database on GI/ASM. It has been applied
with PSU patches regularly with no issue. At the time it had Jan 2016 PSU
on both GI and OHOME.
When I tried to apply the Apr 2016 PSU with the same "opatch auto"
command, it failed with this message right away before it started patching:
Using configuration parameter file: $GI_HOME/crs/install/crsconfig_params
Not able to retreive database home information
(Yes, "retreive" was spelled wrong.)
So I tried to stop the database with "srvctl stop database -d", it failed
too:
PRCD-1027 : Failed to retrieve database XYZ
PRCR-1115 : Failed to find entities of type resource that match filters
((NAME == ora.xyz.db) && (TYPE == ora.database.type)) and contain attributes
VERSION,ORACLE_HOME,DATABASE_TYPE
Cannot communicate with crsd
Then I tried sqlplus> shutdown immediate. It hanged. Tried shutdown abort.
Then just wanted to startup to see if it could. It couldn't. There were
error messages in ASM:
ORA-29786: SIHA attribute GET failed with error [Attribute 'ASM_DISKSTRING'
sts[184] lsts[0]]
But there had not been any changes to the database or ASM since last PSU
patch. The diskstring has been the same and all devices are there with the
correct ownership/permission.
So SA had to power off the server and power it on. After that, ASM started
back fine and the database has been running normal so far.
I opened a Oracle Sev 1 ticket right when the database got stuck starting up,
that was Saturday morning. I even called to escalate the issue and talked
with a support manager after wasting 50 minutes waiting. 3 support engineers
took brief turns asking me to provide logs/info and went off their shifts.
So far I still have no feedback on what might have gone wrong and next time
we attempt patching it again if we will have the same issue.
Do you have any idea what have gone wrong? Any suggestion on checking crsd?
Thanks a bundle,
Chen
--
*--*
*BR*
*Sumit Tyagi*
*+91-7829543355*
