sql

First of all you need to cancel the standby recover process which will apply all the archivelogs and files on the standby side. This can be done by the following command:

SQL> recover managed stanbdy database cancel;

Afterwards you need to adjust the file management parameter to be able to manual change those files:

SQL> alter system set STANDBY_FILE_MANAGEMENT=MANUAL;

Since you already created the logfiles for the standby and the primary as pointed out. You need to shutdown the Standby database at this point, this is not a big deal incase the Standby will ask for all the missing files once it ist started up again.

SQL> shutdown immediate;

To be able to access the file that the standby thinks is in use at this moment, you need to set the following line within your init-file:

*.log_file_name_convert='dummy','dummy';

Restart your standby database.

startup mount;

And now you can drop your logfile goups like this:

SQL> ALTER DATABASE DROP LOGFILE GROUP X;

Now the file and group that has a problem should be deleted and you can recreate it:

ALTER DATABASE
ADD LOGFILE GROUP X ('$PATH/logfile1a.log', '$PATH/logfile1b.log')
SIZE XXXM REUSE;

At this point your standby database should be able to use the file again.

OperatingSystem:

ProgrammingLanguage:

Technology:

First the excel file was converted to a CSV file using LibreOffice Calc.

Then using the web generator https://codebeautify.org/csv-to-sql-converter and entering some database specific details (tablename, columnname identifier, columnname targetvalue) and choosing "CSV to SQL(INSERT)" an SQL script was generated that inserts into each row with the identifier the corresponding value from the CSV file.

The output was saved as an .sql file.
A a database backup created.
Afterwards the sql-file was uploaded into phpMyAdmin as an import script and executed perfectly.

ProgrammingLanguage:

Subscribe to sql