SQL Serevr log flie issue

try this. to truncate your log files.

Use Master
backup log P67 with no_log
 
Use P67
dbcc shrinkfile(<your log fine name>, 0, truncateonly)

Select allOpen in new window

You should backup and truncate
Have a look at the following:

http://support.microsoft.com/kb/317375

Good Luck!

Gary

is it USE Master or
USE P67  

because log for P67 is full

and one more thing i will tell you what i usually do. see below steps---------------

USE [YourDatabaseNameHere]
    GO
    SELECT *
    FROM sysfiles
    WHERE name LIKE '%LOG%'
    GO
     

Second, set the database recovery model to 'simple' if its not simple.

    USE [YourDatabaseNameHere]
    GO
    ALTER DATABASE [YourDatabaseNameHere] SET RECOVERY SIMPLE
    GO
     

Third, issue a checkpoint against the database to write the records from the transaction log to the database.

    USE [YourDatabaseNameHere]
    GO
    CHECKPOINT
    GO
     

Fourth, truncate the transaction log.

    USE [YourDatabaseNameHere]
    GO
    BACKUP LOG [YourDatabaseNameHere] WITH NO_LOG
    GO
     

Fifth, record the logical file name for the transaction log to use in the next step.

    USE [YourDatabaseNameHere]
    GO
    SELECT Name
    FROM sysfiles
    WHERE name LIKE '%LOG%'
    GO

Sixth, to free the unused space in your transaction log and return the space back to the operating system, shrink the transaction log file.

    USE [YourDatabaseNameHere]
    GO
    DBCC SHRINKFILE ([FileNameFromPreviousStep], [NeededFileSize])
    GO
     

Seven, review the database transaction log size to verify it has been reduced.

    USE [YourDatabaseNameHere]
    GO
    SELECT *
    FROM sysfiles
    WHERE name LIKE '%LOG%'
    GO


but as i said earlier disk D stores all mdf files
and Disk L stores all ldf files. but in P67 folder there are two ldf files P66_1  and P66_2 so when i shrink thru above steps the P66_1 got shrinked but the second file P66_2 is the same size. so what should i do. i have only deal with one files until now but now i see two ldf files.

Shrinking the log will NOT help create any new log space. It just removes UNUSED space from the file, which generally won't help at all. You first need to do what the error message says: check log_reuse_wait_desc to find out what the problem is.

Is your database supposed to be in SIMPLE or FULL recovery mode?

the databases are in full recovery modes

OK. Did you determine the cause of the problem yet? See:
http://technet.microsoft.com/en-us/library/ms345414.aspx

Aatish, you can still shrink your log files one by one. Firs go for one and then go for the second one. Hope this resolves your issue.

Is your database enabled for replication. Could you please double check? the replication might be hung and therefore it might be growing up your log file size.

And last but not the least are you taking a backup of your transaction log files, if so how frequently?

now i am not taking backup of the trans logs.

thanks