Search This Blog

Tuesday, November 30, 2021

Oracle : ORA-00333: redo log read error block XXXX count XXXX


As per Oracle information, ORA-00333 is caused by an IO error while reading the log described in the accompanying error. The resolution is to restore accessibility to the file, or get another copy of the file.

First run following command:

1. SQL> Conn sys as sysdba

          Pass: 

 2. SQL> Shutdown immediate;


 3.  SQL> startup mount;


4. SQL> alter system set "_allow_resetlogs_corruption"=true scope=spfile;

 

5. SQL> Shutdown immediate;

6. SQL> alter database open resetlogs;

   Here , you will get error. Then  try next command.


7. SQL>recover database until cancel;

   For any promopt error or anything, just press ENTER ( I followed) .

8. SQL> alter database open resetlogs;


9. SQL> Shutdown immediate;


10. SQL> Startup


After database open, please take backup first then try following. 


11. SQL> Shutdown immediate;


12. SQL> startup mount;


13. SQL> alter system set "_allow_resetlogs_corruption"=false  scope=spfile;

14. SQL> Shutdown immediate;

15. SQL> startup


Wednesday, September 22, 2021

Oracle : oracle weblogic server state changed to force shutting down

 1. try to upgrade existing domain. 

2. You wil find that domain related user like DEV-STB, DEV_OPSS or other password expire. N

3. Now change and unlock using below command


    alter user DEV_OPSS identified by A123  account unlock;


Now, try to start Admin server, form server and reports server in 12C forms

Saturday, August 28, 2021

MSSQL: Decrease/Reduce the size of sql server log file

 

USE Your_Database_Name;
GO
-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE Your_Database_Name
SET RECOVERY SIMPLE; GO DBCC SHRINKFILE (Your_Database_Name_Log, 1); -- Will resize log file to 1 MB.
GO ALTER DATABASE Your_Database_Name -- Reset the database recovery model.
SET RECOVERY FULL; GO

Friday, August 6, 2021

MSSQL: The log scan number (85:368:1) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during start up.

 


 First: Go to this path C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn\Templates


Second: Copy and paste the database/file named model.mdf and modellog.ldf to this path C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA



Now, problem will be resolved !

Tuesday, March 23, 2021

Oracle : ORA-00020: maximum number of processes (150) exceeded

 

ORA-00020: maximum number of processes (150) exceeded


To resolve this error , please follow below steps:

$ sqlplus -prelim "/as sysdba"

   SQL> Conn sys as sysdba

 SQL> shutdown abort

 ORACLE instance shut down.

 SQL> exit

 Disconnected from ORACLE

After this point the database could once again be restarted:

sqlplus / as sysdba


Then run below commands:


sql> alter system set processes=500 scope=spfile;

sql> alter system set sessions=555 scope=spfile;

sql> alter system set transactions=610 scope=spfile;

sql> shutdown abort

sql> startup