SCOM2012 - SQL 2012 DB Log File Discovery isssue

Dear Experts,
I have some SQL 2012 servers, that has few log files (.LDF) stored in a specific drive. SCOM discovers these files but, has a wrong value in 'Display Name'.
For example. The log file name on the server is PROD and the file path c:\SQL\PROD.LDF, but in the console it shows name as UAT and file path as c:\SQL\PROD.LDF (file path is correct as expected). It always stays in critical state stating that the log file
is out of space while it is not the case.
We even have tried wiping the agent off the server and reinstalling it. But it did not fix the issue. When I remove the agent 'Operations Manager' under event log disappears, but when I reinstall the agent after few days, I see the log created,
but with older events too dated well prior to the uninstallation.
And the other thing is, we had this issue while using 2007 R2 and even after switching over to 2012 it continues.
SCOM 2012 was a fresh setup and was not an upgrade.
Hope someone could help me out with this.
Regards,
Saravanan

Hi Niki,
Sorry for the delay in reply.
I hope the image can explain better. I have that log file on a SQL server, which is being discovered with a wrong File name but with the correct path. The actual file name what I see on the server is exactly the same as it shows in the File path in console.
But 'File Name' in the console is completely irrelevant. Also, this log file is in critical state for log file full, which is statistically false. There are few other log files on this server, for which we do not have this issue.
Please let me know if any other information would be required
Regards,
Saravanan

Similar Messages

SQL Server 2012 DB log file doesn't shrink (simple recovery model)

I've found several similar questions in this forum, but none of the answers have resolved my problem: I have a SQL Server 2012 DB using simple recovery model. The MDF file is 12 GB and the LDF file is 10 GB. I'm trying to shrink the size of the
LDF file. I've read that for simple recovery model DBs there are reasons for delaying log file shrinking, but I still can't find a solution based on these reasons.
When I try to shrink it using this command:
DBCC SHRINKFILE(MyDB_log, 1000000)
I get these results, and no change of file size:
DbId FileId CurrentSize MinimumSize UsedPages EstimatedPages8 2 1241328 128 1241328 128
The same results running this:
DBCC SHRINKFILE(MyDB_log, 1000000, TRUNCATEONLY)
There doesn't appear to be any open transactions:
DBCC OPENTRAN()No active open transactions.DBCC execution completed. If DBCC printed error messages, contact your system administrator.
And this returns NOTHING:
SELECT name, database_id, log_reuse_wait_desc FROM sys.databases WHERE database_id = DB_ID()name database_id log_reuse_wait_descMyDB 8 NOTHING
I've also tried running the following, but nothing useful is returned:
SELECT * FROM sys.dm_tran_database_transactionsSELECT * FROM sys.dm_exec_requests WHERE database_id=DB_ID()SELECT * FROM sys.dm_tran_locks WHERE resource_database_id=DB_ID()
Any other suggestions of what I can do to shrink this log file? Or perhaps someone can justify its enormous size?
David Collacott

The answer is pretty simple.
The following code is the problem:
DBCC SHRINKFILE(MyDB_log, 1000000)
You are telling SQL Server that you want to "shrink" the MyDB_log file and the target size is 1TB. Well according to you the MyDB_Log file is well below the 1TB size you are targeting, in fact it's only 10GB so SQL Server is doing precisely what you
are telling it to do.
See, according to the SQL Server documentation
here, target size "Is the size for the file in megabytes, expressed as an integer."
Now if you'd like to actually shrink the log file down to, oh say 1GB, then you should try the following command:
DBCC SHRINKFILE(MyDB_log, 1000)
The theory being 1000 * 1048576 (i.e. 1MB) is equal to 1GB.

Unable to view SQL Request in Log files

Hi Folks,
I am facing an issue which I am unable to find out the solution to view the physical query generated in log files in Presentation Services.
Below is the SQL Request generated but I want to view the exact physical query i.e SQL Request which is hitting DB.
So please guiude me to resolve this issue, I guess it is because of Initialization blocks created which is blocking to view the SQL request.
-------------------- SQL Request:
set variable LOGLEVEL = 7;SELECT "- Policy Effective-Start Date"."Start Quarter" saw_0, "- Insurance Policy Facts".Revenue saw_1, "- Insurance Policy Facts"."# Insurance Policies" saw_2, "Insurance Policy".Status saw_3, "Insurance Policy".Type saw_4 FROM "Insurance Policies" WHERE ("Insurance Policy".Type = 'Policy') AND ("- Policy Effective-Start Date"."Start Julian Day Number" BETWEEN VALUEOF(CURRENT_JULIAN_DAY)-365 AND VALUEOF("CURRENT_JULIAN_DAY")) ORDER BY saw_0, saw_3, saw_4
/* QUERY_SRC_CD='rawSQL' */
Regards
Dj

There is no Enterprise Edition of SSMS. There is SSMS Basic and SSMS Complete. Prior to 2012 sp1, only SSMS Basic were available with Express Edition - but as of 2012 sp1 Expredd also offers SSMS Complete. SSMS Complete is selected bu default when you install
SSMS (unless you are prior to 2012 sp1 and are using Express, of course).
However, even SSMS Basic *should* show Agent assuming you have permissions for that. This is hearsay, but from trusted sources. Here is what to do:
Check what is installed for the machine from where you are running SSMS. You can do that using SQL Server Installation Center - see this blog post: http://sqlblog.com/blogs/tibor_karaszi/archive/2011/02/10/what-does-this-express-edition-look-like-anyhow.aspx
(towards the end).
On that machine try both this problematic account as well as an account which is sysadmin. Does the sysadmin account see Agent? If so, you know permissions aren't granted properly. If not, then you know the tool is the problme.
Also try the problematic account from a machine where you know you see Agent normally. Again, this will help you assess whether the problem is the tool (SSMS) or permissions for the account.
Tibor Karaszi, SQL Server MVP |
web | blog

Help! SQL server database log file increasing enormously

I have 5 SSIS jobs running in sql server job agent and some of them are pulling transactional data into our database over the interval of 4 hours frequently. The problem is log file of our database is growing rapidly which means in a day, it eats up 160GB of
disk space. Since our requirement dont need In-point recovery, so I set the recovery model to SIMPLE, eventhough I set it to SIMPLE, the log
data consumes more than 160GB in a day. Because of disk full, the scheduled jobs getting failed often.Temporarily I am doing DETACH approach
to cleanup the log.
FYI: All the SSIS packages in the job is using Transaction on
some tasks. for eg. Sequence Cointainer
I want a permanent solution to keep log file in a particular memory limit and as I said earlier I dont want my log data for future In-Point recovery, so no need to take log backup at all.
And one more problem is that in our database,the transactional table has 10 million records in it and some master tables have over 1000 records on them but our mdf file
size is about 50 GB now.I dont believe that this 10 million records should make it to 50GB memory consumption.Whats the problem here?
Help me on these issues. Thanks in advance.

And one more problem is that in our database,the transactional table has 10 million records in it and some master tables have over 1000 records on them but our mdf file
size is about 50 GB now.I dont believe that this 10 million records should make it to 50GB memory consumption.Whats the problem here?
Help me on these issues.
For SSIS part of question it would be better if you ask in SSIS forum although noting is going to change about logging behavior. You can increase some space on log file and also should batch your transactions as already suggested
Regarding memory question about SQL Server, once it utilizes memory is not going to release unless there is windows OS faces memory pressure and SQLOS asks SQL Server to trim down its memory consumption. So again if you have set max server memory to some
where near 50 SQL Server will utilize that much memory eventually. So what you are seeing is totally normal. Remember its costtly task for SQL Server to release and take memory so it avoids it by caching as much as possible plus it caches more so as to avoid
physical reads which are costly
When log file is getting full what does below transaction return
select log_reuse_wait_desc from sys.databases where name='db_name'
Can you manually introduce chekpoint in ETL query. Try this it might help you
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

FDM-generated SQL statement in log file?

Hello all, hopefully a simple question:
When you perform an import using FDM, I know that behind the scenes a SQL SELECT statement is composed and executed against the database server. My question: is the actual SQL statement kept in a log somewhere (so that we can see it?) In our case it's an Oracle DB server and we're using the ERPI Adapter; not sure if that's relevant. We would like to grab that SQL statement and use it as a jumping-off point for some other things.
Thanks in advance for anything you can offer.

The SQL Statement is not written to the log for the adapter. The only things that are logged are what show in the adapter log file if you enable loggin for the ERPi source adapter in the "Get Data" action.

SQL 2012 SP1 DB Engine discovery; incorrect version

Hi All
I've added the latest SQL MPs (6.4.1.0) to our SCOM 2012 R2 instance and have been working through the steps to get our 2008 and 2012 DBs added and monitored by SCOM. The 2008 db's have gone in fine, but I noticed that our 2012 db's are visible but are not
monitored.
What I've noticed is that the "SQL Server 2012 DB Engine Group" has not been populated (unlike the 2008 engine groups) and looking at the dynamic inclusion rule, it's trying to match the wildcard 11.0.*. This is where it gets interesting, because
I can see from querying the SQL server directly that each 2012 instance has a version of 11.0.3000.0, but the version under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SQLServer2012\CurrentVersion is 11.1.3000.0. The engine version
that SCOM reports is also 11.1.3000.0, so I assume that it's picking up this as the version and is therefore not adding the SQL 2012 instance to the DB Engine Group because it doesn't match the 11.0.* wildcard.
Whilst I've found one or two articles that refer to this problem (specifically http://ianblythmanagement.wordpress.com/2013/09/12/sql-server-2012-db-engine-group-problem), I can't work how to get around this problem and get these 2012 dbs monitoring
in SCOM. I don't fancy attempting to change version number on the SQL servers, and I can't work out a way to amend or override the 2012 Discovery MP to also pick up 11.1.* versions.
Does anyone have any ideas on how to work around this (other than wait for an update to the MP and hope it's fixed there !) ?
Cheers
Neil

Hi,
The issue has been report to Microsoft feedback here.
http://connect.microsoft.com/SQLServer/feedback/details/813297/sql-server-2012-sp1-setup-sets-incorrect-version-number-in-the-registry
You can create a custom group with the rule. ( Object is SQL Server 2012 DB Engine AND ( Version Matches wildcard 11.1.* ) AND True )
Niki Han
TechNet Community Support

Sql server 2005 log file shrinking issue.

hi,
one of my production server database log file size is increasing continuously,we can take log backup but no use,
we can change the database recovery model from full to simple we shrink the log file, log file shrink successfully but space is not released,and we are getting the alerts continuously your physical disk is 95% like that.
here what we can do how reduced the log file size and how to control the log file size.
please give me the answer ASAP.
Thanks,

Hello,
In SQL Server, log truncation occurs automatically as follows:
• Under the simple recovery model, after a checkpoint.
• Under the full recovery model or bulk-logged recovery model, after a log backup, if a checkpoint has occurred since the previous backup.
As Dan posted earlier, when we run the above code, we will get an integer value. The log_reuse_wait_desc value tells us why the transaction log space is not reused. You can refer to the article below to check the root cause.
http://msdn.microsoft.com/en-us/library/ms345414.aspx
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

SQL Loader Inserting Log File Statistics to a table

Hello.
I'm contemplating how to approach gathering the statistics from the SQL Loader log file to insert them into a table. I've approached this from a Korn Shell Script perspective previously, but now that I'm working in a Windows environment and my peers aren't keen about batch files and scripting I thought I'd attempt to use SQL Loader itself to read the log file and insert one or more records into a table that tracks data uploads. Has anyone created a control file that accomplishes this?
My current environment:
Windows 2003 Server
SQL*Loader: Release 10.2.0.1.0
Thanks,
Luke

Hello.
Learned a little about inserting into multiple tables with delimited records. Here is my current tested control file:
LOAD DATA
APPEND
INTO TABLE upload_log
WHEN (1:12) = 'SQL*Loader: '
FIELDS TERMINATED BY WHITESPACE
TRAILING NULLCOLS
( upload_log_id   RECNUM
, filler_field_0 FILLER
, filler_field_1 FILLER
, filler_field_2 FILLER
, filler_field_3 FILLER
, filler_field_4 FILLER
, filler_field_5 FILLER
, day_of_week
, month
, day_of_month
, time_of_day
, year
, log_started_on          "TO_DATE((:month ||' '|| :day_of_month ||' '|| :time_of_day ||' '|| :year), 'Mon DD HH24:MI:SS YYYY')"
INTO TABLE upload_log
WHEN (1:11) = 'Data File: '
FIELDS TERMINATED BY ':'
( upload_log_id    RECNUM
, filler_field_0   FILLER POSITION(1)
, input_file_name          "TRIM(:input_file_name)"
INTO TABLE upload_log
WHEN (1:6) = 'Table '
FIELDS TERMINATED BY WHITESPACE
( upload_log_id   RECNUM
, filler_field_0 FILLER POSITION(1)
, table_name              "RTRIM(:table_name, ',')"
INTO TABLE upload_rejects
WHEN (1:7) = 'Record '
FIELDS TERMINATED BY ':'
( upload_rejects_id RECNUM
, record_number      POSITION(1) "TO_NUMBER(SUBSTR(:record_number,8,20))"
, reason
INTO TABLE upload_rejects
WHEN (1:4) = 'ORA-'
FIELDS TERMINATED BY ':'
( upload_rejects_id RECNUM
, error_code         POSITION(1)
, error_desc
INTO TABLE upload_log
WHEN (1:22) = 'Total logical records '
FIELDS TERMINATED BY WHITESPACE
( upload_log_id      RECNUM
, filler_field_0     FILLER POSITION(1)
, filler_field_1     FILLER
, filler_field_2     FILLER
, action                     "RTRIM(:action, ':')"
, number_of_records
INTO TABLE upload_log
WHEN (1:13) = 'Run began on '
FIELDS TERMINATED BY WHITESPACE
TRAILING NULLCOLS
( upload_log_id   RECNUM
, filler_field_0 FILLER POSITION(1)
, filler_field_1 FILLER
, filler_field_2 FILLER
, day_of_week
, month
, day_of_month
, time_of_day
, year
, run_began_on            "TO_DATE((:month ||' '|| :day_of_month ||' '|| :time_of_day ||' '|| :year), 'Mon DD HH24:MI:SS YYYY')"
INTO TABLE upload_log
WHEN (1:13) = 'Run ended on '
FIELDS TERMINATED BY WHITESPACE
TRAILING NULLCOLS
( upload_log_id   RECNUM
, filler_field_0 FILLER POSITION(1)
, filler_field_1 FILLER
, filler_field_2 FILLER
, day_of_week
, month
, day_of_month
, time_of_day
, year
, run_ended_on            "TO_DATE((:month ||' '|| :day_of_month ||' '|| :time_of_day ||' '|| :year), 'Mon DD HH24:MI:SS YYYY')"
INTO TABLE upload_log
WHEN (1:18) = 'Elapsed time was: '
FIELDS TERMINATED BY ':'
( upload_log_id   RECNUM
, filler_field_0 FILLER POSITION(1)
, filler_field_1 FILLER
, filler_field_2 FILLER
, elapsed_time
INTO TABLE upload_log
WHEN (1:14) = 'CPU time was: '
FIELDS TERMINATED BY ':'
( upload_log_id   RECNUM
, filler_field_0 FILLER POSITION(1)
, filler_field_1 FILLER
, filler_field_2 FILLER
, cpu_time
)Here are the basic table create scripts:
TRUNCATE TABLE upload_log;
DROP TABLE upload_log;
CREATE TABLE upload_log
( upload_log_id      INTEGER
, day_of_week        VARCHAR2( 3)
, month              VARCHAR2( 3)
, day_of_month       INTEGER
, time_of_day        VARCHAR2( 8)
, year               INTEGER
, log_started_on     DATE
, input_file_name    VARCHAR2(255)
, table_name         VARCHAR2( 30)
, action             VARCHAR2( 10)
, number_of_records INTEGER
, run_began_on       DATE
, run_ended_on       DATE
, elapsed_time       VARCHAR2( 8)
, cpu_time           VARCHAR2( 8)
TRUNCATE TABLE upload_rejects;
DROP TABLE upload_rejects;
CREATE TABLE upload_rejects
( upload_rejects_id INTEGER
, record_number      INTEGER
, reason             VARCHAR2(255)
, error_code         VARCHAR2( 9)
, error_desc         VARCHAR2(255)
);Now, if I could only insert a single record to the upload_log table (per table logged); adding separate columns for skipped, read, rejected, discarded quantities. Any advice on how to use SQL Loader to do this (writing a procedure would be fairly simple, but I'd like to perform all of the work in one place if at all possible)?
Thanks,
Luke
Edited by: Luke Mackey on Nov 12, 2009 4:28 PM

Truncate SQL 2008 R2 log files

How do I truncate a log file. Running out of space.
Help is appreciated.
Thanks
Dave Kozlowski

If your db is in Full Recovery:
ALTER DATABASE
[DatabaseName] SET
RECOVERY SIMPLE WITH
NO_WAIT
DBCC SHRINKFILE
([LogFileName, 1)
ALTER DATABASE [DatabaseName]
SET RECOVERY
FULL WITH NO_WAIT
GO
Ayad

Error restoring SQL 2008 R2 DB into SQL 2012: BACKUP LOG cannot be performed because there is no current database backup.

I have a SQL 2008 R2 database that I am trying to move to 2012. Made a full backup of the database in 2008 R2. Recovery model is Simple, compatibility level is 2008 Went to 2012, created a dummy database, did Tasks--> Restore -->
Database , located the backup file, selected it, changed the file locations and tried to restore the backup (with overwrite option), got the following error:
BACKUP LOG cannot be performed because there is no current database backup.
This is a simple task that has always worked in 2008 R2. Does anyone know what the problem is and a possible solution?
Thanks

Hi,
This error occurs when the database recovery model has been changed to Simple and/or the recovery model has been changed back to Full but a full backup has not been performed since the change.
If a full backup has been performed, the following conditions will require that another full backup be taken:
· The recovery model had been changed without taking a full backup
· A SQL maintenance plan task had changed the recovery model (reindexing can cause this)
· A backup specifying TRUNCATE_ONLY had been run on the database
· The database was detached from another server and attached to the current server
Additionally, if we take full database backup after the Database is set to readonly, Then transaction log backup we will end up with this error. This is expected behavior. I have list an example within the link below.
Please check above conditions and fix your issue, if you have any concern, please let me know.
Example:
BACKUP LOG cannot be performed because there is no current database backup.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/b5c36e60-836f-4c9e-b9d7-3fb3f3ee4d37/backup-log-cannot-be-performed-because-there-is-no-current-database-backup
Thanks
Candy Zhou

How to configure log files in SQL 2012?

I'm installing a SharePoint Solution and using Microsoft SQL 2012 and I have limited knowledge in installing SQL. I simply run the wizard and create the DB for SharePoint.
Is there any links/materials available demonstrating how to correctly configure the log files step by step in a specific partition during the SQL installation for SharePoint 2013?
thanks,

Hello,
SQL Server database log files benefit from RAID 1 and RAID 10 configurations. RAID 10 is recommended for both data files and log files.
To control de grow of transaction log files, please backup them regularly. The following article may explain you in detail why:
http://technet.microsoft.com/en-us/library/ms175495.aspx
Monitor the growth of log files using Performance Monitor and the SQLServer:Databases --> Log Growths counter. Adjust the size of log files until Log Growths
is constantly zero.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Odi 11g - IKM SQL to Hyperion Essbase (DATA) log file always empty

In odi 11g when using *"IKM SQL to Hyperion Essbase (DATA)"* setting the the "LOG_ENABLED" = true,
only an empty file are generated.
Just "LOG_ERRORS" file (if errors occurs) are created.
Is this just an my issue?
Can someone help me?
p.s.: the same issue, I got even with the *"IKM SQL to Hyperion Planning"*
Thx in advance, Paolo

Thanks John for your suggestion.
here the patch *"Patch 10302682: IKM SQL TO PLANNING: LOG FILE IS CREATED BUT NOTHING INSIDE."*
I didn't see any other about Essbase...
I try to check all day on support site.
Paolo
Edited by: Paolo on 19-apr-2011 8.44

Installing SQL 2012 SP2 - The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Hi,
I am trying to install the SQL 2012 SP2 in one of the servers. I am getting the error as :
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Error code 0x84B10001.
The same setup is working in other servers, but on a particular server I am getting this error.
Server configuration: Windows server 2008 r2 standard edition, servvice pack 1 , 64 bit OS
How to fix this?
Thanks

Hi Venkatzeus,
Based on my research, the issue is caused by that some .dll files are corrupt or missing during the installing of SQL Server 2012 SP2.
In order to troubleshoot this issue, please view the detail error message in SQL Server Setup Log Files. We can read the Summary text under %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log\, and the Detail text in the place %programfiles%\Microsoft
SQL Server\110\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\Detail.txt. For more details, please see:
View and Read SQL Server Setup Log Files
Besides, here are some similar issues for your references:
https://social.technet.microsoft.com/Forums/en-US/29e3cef1-4699-4710-9aa5-d56cf4a279c5/the-specified-module-could-not-be-found-exception-from-hresult-0x8007007e-systemwindowsforms?forum=sqlanalysisservices
https://social.technet.microsoft.com/Forums/en-US/b2faae67-19af-4f50-88c6-5a427556df3e/error-encountered-when-creating-new-integration-services-project-0x8007007e?forum=sqlintegrationservices
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

How to create a Log file on Client machine

Hi All,
I am trying to create a log file on my local machine using TEXT_IO.FILE_TYPE in a stored procedure but it is throwing a compiler error as Error(5,10): PLS-00201: identifier 'TEXT_IO.FILE_TYPE' must be declared. I seem it is occuring because of WebUtil and I am using Oracle SQL Developer on my machine.
Is there any way to create log file on local machine.Can anyone help me out, Since three day I am struging to get out from this.
With regards
R e h a n

Hi,
TEXT_IO.FILE_TYPE Package is used in Oracle Forms. Please Post in the relevant Forum for Questions for these.
Forms
You can Use the UTL_FILE in PL/SQL to create Log Files on the database server directory and Share the directory.
Thanks,
Shankar.

Log file full

Hi,
My log file is full, steps to reduce the size of the logfile?

Old question: While drafting question you get similar questions . If you whould have read that , you might have fixed same till now.
Btw if below solution doesnt work you can check :Sql Server Transaction Log File Is Not Shrinking
Thanks Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem

SCOM2012 - SQL 2012 DB Log File Discovery isssue

Similar Messages

Maybe you are looking for