on 07-10-2009 7:24 PM
Friends,
I am having 2 drives for MSSQL DB.
File system
G: SAPDATA 1,2 ,3 - size 1 TB (RAID 5)
H: PRDLOG1 - size 90 gb. (RAID 1)
When my PRD server is running all 90 gb of PRDLOG1 is full in H :drive & throws a n error in sap SNAP_NO_NEW_ENtry.
I understood i has no space to write log file & i created a new logfile in G: drive with name PRDLOG2 7 contuied with all the PRd activities with oyt any interruption.
after creating my file system as follows.
G: SAPDATA 1,2 ,3 & PRDLOG2 - size 1 TB (RAID 5)
H: PRDLOG1 - size 90 gb (RAID1)
as PRDLOG2 is on RAID5 performance is badly hitted with bottle necks.
******************************************************************************************************************************************
Now i have taken backup of full DB. & try shrink log PRDLOG1 & planned to move PRDLOG2 from G drive to H drive.
So my system will start working like before .
When i am trying t shrink file PRDLOG1using query dbcc shrinkfile(PRDLOG1, 50) it is running successful & i am getting following message.
Cannot shrink log file 2 (PRDLOG1) because all logical log files are in use.
1 rows affected.
if dbcc trows an error contact your systems administrator
how should i overcome this issue. as im basicaly an oracle guy i am finding hard to understand this messages.
Request to provide some support from any MS-SQL guys.
rgds,
rahul..
Actually the below link helped in shrinking file & i have followed sap note....
625546 Size of transaction log file is too big
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rahul,
I had same issue and I stopped SAP and MSSQL completely. Restarted them and tried to shrink and it worked for me. I am not sure if you can bounce your PROD system, if you can bounce I would recommend to give it a try
Thanks,
Praveen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rahul,
I beleive you need to have free space on disk to perform shrink, can you move the LOG file to other location with more free space and then try shrinking it.
It is possible to shrink the transaction log file while the SQL Server database is online, however if transactions are taking place while the operation is running you may experience this error. Try running it in off hours the DBCC SHRINKFILE command in off hours, or shut down access to the database from other apps (SAP).
Make sure that there are no running transactions, by running the command on the database in question: DBCC OPENTRAN
Thanks,
Praveen
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.