ORA-29288: invalid file name
Cause: A NULL or zero length file name was specified
Action: Correct the file name to be a nonzero length string
https://support.oracle.com/
http://www.oracle.com/
ORA-29288: invalid file name
Cause: A NULL or zero length file name was specified
Action: Correct the file name to be a nonzero length string
https://support.oracle.com/
http://www.oracle.com/
ORA-16723: setting AlternateLocation property conflicts with the redo transport setting
Cause: The standby database is not using standby redo logs, and the redo transport service to the standby database is set with a nonzero value of ReopenSecs and a zero value of MaxFailure. In this case, the redo transport service will retry the standby destination indefinitely and never switch to the alternate destination.
Action: Any one of the following actions will solve the problem: (1) add standby redo logs to the standby database; (2) set ReopenSecs property to zero; (3) set MaxFailure property to a nonzero value. After executing one of the above actions, reset the AlternateLocation property.
NZE-43021: pkcs11: Certificate with given cert label is not a user cert
Cause: The certificate with the specified certificate label did not have a matching private key in the smart card/HSM.
Action: Follow smart card/HSM vendor instructions to create credentials (certificate/private key) in smart card/HSM.
NZE-43020: pkcs11: Multiple certificates found on smart card/HSM with given cert label
Cause: Certificates with identical labels were found in the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to assign unique certificate labels to certificates.
NZE-43019: pkcs11: No certificate found on smart card/HSM label with given cert label
Cause: There were no certificate labels on the smart card/HSM that matched the certificate label specified in the wallet.
Action: Follow smart card/HSM vendor documentation to set certificate label in smart card/HSM.
NZE-43018: pkcs11: No user certificate found on the smart card/HSM
Cause: No user certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart card/HSM with certificate and private key.
NZE-43017: pkcs11: No certificate found on the smart card/HSM
Cause: No certificate was found on the smart card/HSM.
Action: Follow smart card/HSM vendor documentation to populate the smart card/HSM with certificate.
NZE-43015: pkcs11: key pair gen error
Cause: error occurred while generating key pair using HSM
Action: Check trace message
NZE-43014: pkcs11: finding private key on token error
Cause: error occurred while finding private key on token
Action: Make sure the private key corresponding to the certificate in wallet is on the token. Check trace message
NZE-43011: pkcs11: Token login failed
Cause: To login to the pkcs11 token a correct passphrase is needed
Action: Check the token passphrase.