Langsung ke konten utama

OPW-00005: File with same name exists - please delete or rename

OPW-00005: File with same name exists - please delete or rename:

Solving

oracle@unknown:/u01/oracle/products/12/dbhome_1/dbs$ mv orapworcl orapworcl.bak

oracle@unknown:/u01/oracle/products/12/dbhome_1/dbs$ orapwd file=$ORACLE_HOME/dbs/orapworcl password=passwordDB

Komentar

Postingan populer dari blog ini

Mounting USB drives in Windows Subsystem for Linux

Windows Subsystem for Linux can use (mount): SD card USB drives CD drives (CDFS) Network drives UNC paths Local storage / drives Drives formatted as FAT, ExFAT or NTFS can be mounted in WSL. For this example, we assume the drive shows in Windows as F:\ If Windows changes the USB drive letter on a subsequent session, you need to repeat this process. The commands are typed into the Windows Subsystem for Linux Terminal. Create a mount location in WSL: $ sudo mkdir /mnt/f Mount the drive in WSL: $ sudo mount -t drvfs f: /mnt/f After this one-time setup, one can create and manipulate files from both Windows and WSL on the same drive. network storage Here we assume: networked storage is already showing in Windows under \\server\share we want to access this network storage from WSL as /mnt/share Create a mount location in WSL: $ sudo mkdir /mnt/share Mount the network share in WSL: $ sudo mount -t drvfs '\\server\share' /mnt/share

FMW 12.2.1.3.0: "ONS configuration failed" or "oracle.ons.NoServersAvailable: Subscription time out"

FMW 12.2.1.3.0: "ONS configuration failed" or "oracle.ons.NoServersAvailable: Subscription time out" Solving To implement the workaround in the Configuration Wizard(config.sh) set the following environment variable before launching config.sh. $ export CONFIG_JVM_ARGS=-Doracle.jdbc.fanEnabled=false

ERROR ORACLE DB: The version 12.2.0.1.0 of the database that you are using is not a supported version

ERROR ORACLE DB: The version 12.2.0.1.0 of the database that you are using is not a supported version or The specified user may not have sufficient privileges to perform this operation. User should have sysdba or dba privileges. Solution SQL> alter system set db_32k_cache_size = 512M scope=both;