Purging Logs for AS Database

Does anyone know of any way to purge AS database logs based on a "time" setting as opposed to a "size" setting?

According to the fine Oracle® Utilities Application Framework Administration Guide Chapter 17, "Archiving and Purging" is readily available to CC&B.

Similar Messages

Recommended Third Party Archive and Purging Software for Oracle Database (Oracle CC&B)

Hi,
We are currently exploring third party archive and purging software for Oracle Database specifically used by an Oracle Customer Care and Billing implementation. Our current data is growing that we think archiving and purging is a now a viable option. Thanks.
Regards,
Dennis

According to the fine Oracle® Utilities Application Framework Administration Guide Chapter 17, "Archiving and Purging" is readily available to CC&B.

SQL0964C The transaction log for the database is full

Hi,
i am planning to do QAS refresh from PRD system using Client export\import method. i have done export in PRD and the same has been moved to QAS then started imported.
DB Size:160gb
DB:DB2 9.7
os: windows 2008.
I facing SQL0964C The transaction log for the database is full issue while client import and regarding this i have raised incident to SAP then they replied to increase some parameter like(LOGPRIMARY,LOGSECOND,LOGFILSIZ) temporarily and revert them back after the import. Based on that i have increased from as below mentioned calculation.
the filesystem size of /db2/<SID>/log_dir should be greater than LOGFILSIZ*4*(Sum of LOGPRIMARY+LOGSECONDARY) KB
From:
Log file size (4KB)                         (LOGFILSIZ) = 60000
Number of primary log files                (LOGPRIMARY) = 50
Number of secondary log files               (LOGSECOND) = 100
Total drive space required: 33GB
To:
Log file size (4KB)                         (LOGFILSIZ) = 70000
Number of primary log files                (LOGPRIMARY) = 60
Number of secondary log files               (LOGSECOND) = 120
Total drive space required: 47GB
But still facing the same issue. Please help me to resolve the ASAP.
Last error TP log details:
3 ETW674Xstart import of "R3TRTABUFAGLFLEX08" ...
4 ETW000   1 entry from FAGLFLEX08 (210) deleted.
4 ETW000   1 entry for FAGLFLEX08 inserted (210*).
4 ETW675 end import of "R3TRTABUFAGLFLEX08".
3 ETW674Xstart import of "R3TRTABUFAGLFLEXA" ...
4 ETW000 [     dev trc,00000] Fri Jun 27 02:20:21 2014                                             -774509399 65811.628079
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                    85 65811.628164
4 ETW000 [     dev trc,00000] &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C The transaction log for the database is full.
4 ETW000                                                                                                  83 65811.628247
4 ETW000 [     dev trc,00000] &+     SQLSTATE=57011 row=1
4 ETW000                                                                                                  51 65811.628298
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  67 65811.628365
4 ETW000 [     dev trc,00000] &+     DELETE FROM "FAGLFLEXA" WHERE "RCLNT" = ?
4 ETW000                                                                                                  62 65811.628427
4 ETW000 [     dev trc,00000] &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=8, reopt=0
4 ETW000                                                                                                  58 65811.628485
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  53 65811.628538
4 ETW000 [     dev trc,00000] &+     Input SQLDA:
4 ETW000                                                                                                  52 65811.628590
4 ETW000 [     dev trc,00000] &+                        1 CT=WCHAR           T=VARCHAR         L=6     P=9     S=0
4 ETW000                                                                                                  49 65811.628639
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.628689
4 ETW000 [     dev trc,00000] &+     Input data:
4 ETW000                                                                                                  49 65811.628738
4 ETW000 [     dev trc,00000] &+     row 1:             1 WCHAR           I=6       "210"               34 65811.628772
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.628823
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.628873
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              27 65811.628900
4 ETW000 [    dbtran ,00000] ***LOG BY4=>sql error -964   performing DEL on table FAGLFLEXA
4 ETW000                                                                                                3428 65811.632328
4 ETW000 [    dbtran ,00000] ***LOG BY0=>SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
4 ETW000                                                                                                  46 65811.632374
4 ETW000 [     dev trc,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                             59 65811.632433
4 ETW000                         RSLT: {dbsl=99, tran=1}
4 ETW000                         FHDR: {tab='FAGLFLEXA', fcode=194, mode=2, bpb=0, dbcnt=0, crsr=0,
4 ETW000                                hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
4 ETW000                                init:p=0000000000000000, init:#=0, wa:p=0X00000000020290C0, wa:#=10000}
4 ETW000 [     dev trc,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'DEL'                            126 65811.632559
4 ETW000                         STMT: {stmt:#=0, bndfld:#=1, prop=0, distinct=0,
4 ETW000                                fld:#=0, alias:p=0000000000000000, fupd:#=0, tab:#=1, where:#=2,
4 ETW000                                groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000                         CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=1, fae:blk=0,
4 ETW000                                con:id=0, con:vndr=7, val=2,
4 ETW000                                key:#=3, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=0X00000001421A3000}
2EETW125 SQL error "-964" during "-964" access: "SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1"
4 ETW690 COMMIT "14208" "-1"
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] CON = 0 (BEGIN)                 16208 65811.648767
4 ETW000 [     dev trc,00000] &+     DbSlModifyDB6( SQLExecute ): [IBM][CLI Driver][DB2/NT64] SQL0964C The transaction log for the database is full.
4 ETW000                                                                                                  75 65811.648842
4 ETW000 [     dev trc,00000] &+     SQLSTATE=57011 row=1
4 ETW000                                                                                                  52 65811.648894
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.648945
4 ETW000 [     dev trc,00000] &+     INSERT INTO DDLOG (SYSTEMID, TIMESTAMP, NBLENGTH, NOTEBOOK) VALUES ( ? , CHAR(   CURRENT TIMESTAMP - CURRENT TIME
4 ETW000                                                                                                  50 65811.648995
4 ETW000 [     dev trc,00000] &+     ZONE   ), ?, ? )
4 ETW000                                                                                                  49 65811.649044
4 ETW000 [     dev trc,00000] &+       cursor type=NO_HOLD, isolation=UR, cc_release=YES, optlevel=5, degree=1, op_type=15, reopt=0
4 ETW000                                                                                                  55 65811.649099
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  49 65811.649148
4 ETW000 [     dev trc,00000] &+     Input SQLDA:
4 ETW000                                                                                                  50 65811.649198
4 ETW000 [     dev trc,00000] &+                        1 CT=WCHAR           T=VARCHAR         L=44    P=66    S=0
4 ETW000                                                                                                  47 65811.649245
4 ETW000 [     dev trc,00000] &+                        2 CT=SHORT           T=SMALLINT        L=2     P=2     S=0
4 ETW000                                                                                                  48 65811.649293
4 ETW000 [     dev trc,00000] &+                        3 CT=BINARY          T=VARBINARY       L=32000 P=32000 S=0
4 ETW000                                                                                                  47 65811.649340
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  50 65811.649390
4 ETW000 [     dev trc,00000] &+     Input data:
4 ETW000                                                                                                  49 65811.649439
4 ETW000 [     dev trc,00000] &+     row 1:             1 WCHAR           I=14      "R3trans"           32 65811.649471
4 ETW000 [     dev trc,00000] &+                        2 SHORT           I=2        12744              32 65811.649503
4 ETW000 [     dev trc,00000] &+                        3 BINARY          I=12744   00600306003200300030003900300033003300310031003300320036003400390000...
4 ETW000                                                                                                  64 65811.649567
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  52 65811.649619
4 ETW000 [     dev trc,00000] &+
4 ETW000                                                                                                  51 65811.649670
4 ETW000 [     dev trc,00000] *** ERROR in DB6Execute[dbdb6.c, 4980] (END)                              28 65811.649698
4 ETW000 [    dbsyntsp,00000] ***LOG BY4=>sql error -964   performing SEL on table DDLOG                36 65811.649734
4 ETW000 [    dbsyntsp,00000] ***LOG BY0=>SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1
4 ETW000                                                                                                  46 65811.649780
4 ETW000 [    dbsync ,00000] ***LOG BZY=>unexpected return code 2          calling ins_ddlog           37 65811.649817
4 ETW000 [     dev trc,00000] db_syflush (TRUE) failed                                                  26 65811.649843
4 ETW000 [     dev trc,00000] db_con_commit received error 1024 in before-commit action, returning 8
4 ETW000                                                                                                  57 65811.649900
4 ETW000 [    dbeh.c ,00000] *** ERROR => missing return code handler                               1974 65811.651874
4 ETW000                         caller does not handle code 1024 from dblink#5[321]
4 ETW000                         ==> calling sap_dext to abort transaction
2EETW000 sap_dext called with msgnr "900":
2EETW125 SQL error "-964" during "-964" access: "SQL0964C The transaction log for the database is full. SQLSTATE=57011 row=1"
1 ETP154 MAIN IMPORT
1 ETP110 end date and time   : "20140627022021"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Regards,
Rajesh

Hi Babu,
I believe you should have taken a restart of your system if log primary are changed. If so, then increase log primary to 120 and secondary to 80 provide size and space are enough.
Note 1293475 - DB6: Transaction Log Full
Note 1308895 - DB6: File System for Transaction Log is Full
Note: 495297 - DB6: Monitoring transaction log
Regards,
Divyanshu

Purge script for 11g database

Hi All,
I have a database with version
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit ProductionI have a purge script to purge the database which is not working. Can anyone tell has oracle released any purge scripts for purging 11G database.
DECLARE
   MAX_CREATION_DATE timestamp;
   MIN_CREATION_DATE timestamp;
   batch_size integer;
   max_runtime integer;
   retention_period timestamp;
BEGIN
   MIN_CREATION_DATE := to_timestamp('2012-03-10','YYYY-MM-DD');
   MAX_CREATION_DATE := to_timestamp('2012-03-20','YYYY-MM-DD');
    max_runtime := 20;
    retention_period := to_timestamp('2012-03-20','YYYY-MM-DD');
   batch_size := 20000;
     soa.delete_instances(
     min_creation_date => MIN_CREATION_DATE,
     max_creation_date => MAX_CREATION_DATE,
     batch_size => batch_size,
     max_runtime => max_runtime,
     retention_period => retention_period,
     purge_partitioned_component => false);
END;Thanks
DUOS

You need to be more specific.
First, you said that you wanted to purge your database, and then the tablespace, and finally, some tables...
If you want to flush data from a table completelly, use TRUNCATE TABLE.
If you want to remove some rows of that table, use DELETE FROM TABLE WHERE [your condition here]

The transaction log for database 'Test_db' is full due to 'LOG_BACKUP'

My dear All,
Came up with another issue:
App team is pushing the data from one Prod1 server 'test_1db' to another Prod2 server 'User_db' through a job, here while pushing the data after some duration job is failing and throwing the following error
'Error: 9002, Severity: 17, State: 2.'The transaction log for database 'User_db' is full due to 'LOG_BACKUP'''.
On Prod2 server 'User_db' log is having enough space 400gb on drive and growth is 250mb. I really confused that why job is failing as there is lot of space available. Kindly guide me to troubleshoot the issue as this issue is occuring from more than
1 week. Kindly refer the screenshot for the same.
Environment: SQL Server 2012 with sp1 Ent-edition. and log backup duration is every 15 mints and there is no High availability between the servers.
Note: Changing to simple recovery model may resolve but App team is required to run in Full recovery model as they need of log backups.
Thanks in advance,
Nagesh
Nagesh

Dear V,
Thanks for the susggestions.
I have followed some steps to resolve the issue, as of now my jobs are working without issue.
Steps:
Generating log backup for every 5 minutes
Increased the growth 500mb to unrestricted.
Once whole job completed we are shrinking the log file.
Nagesh

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

You want to know the amount of space the transaction log for the Customer database is using. Which T-SQL command would you use?

Forced me to do a little research.
DBCC SQLPERF(logspace)
See also
http://stackoverflow.com/questions/198343/how-can-i-get-the-size-of-the-transaction-log-in-sql-2005-programmatically
For every expert, there is an equal and opposite expert. - Becker's Law
My blog
My TechNet articles

The transaction log for database 'SharePoint_Config' is full

Hi all ,
I am very new to sharepoint. when i tried to remove a wsp file from central administration i got the message like
The transaction log for database 'SharePoint_Config' is full. To find out why space in the log cannot
be reused, see the log_reuse_wait_desc column in sys.databases.
Can anybody help me to solve this please. I saw one solution in net like this but i don't know how to do this. Can anybody help me how to do these steps please.
1.
Take the configuration database offline and detach it
2.
Copy the current MDF to a new location (to be used as a way of recovering the database if needed)
3.
Put the database back on-line, reattach it and then put it within simple mode (from full), with an aim of this stopping the database from
increasing in size
4.
Shrink the database and recover log space
5.
Should the shrinking fail, we'd look at detaching the database, making a sideways copy of the log file to another database
6.
We would then reattach the database, which should generate a new log file
Thank you

Hi Soumya,
I don't have any dba resource. And it is not a lab environment. It's Corporate environment.
Thanks alot for ur quick reply.
I normally don't just come onto the threads and tell people that they need a consultant, but you might want to look at getting a consultant to help make sure that your SharePoint environment is health and can be restored in the event of a server failure.
Based on the problem that you have described it might not be recoverable, or at least it might not be as recoverable as you want it to be.
At the very least you'll want to watch this video of my session at TechEd 2014 which talks about backups and how to set them up.
http://channel9.msdn.com/events/TechEd/NorthAmerica/2014/DBI-B214#fbid=
Thank You,
Denny Cherry

How to use the mirrored and log shipped secondary database for update or insert operations

Hi,
I am doing a DR Test where I need to test the mirrored and log shipped secondary database but without stopping the mirroring or log shipping procedures. Is there a way to get the data out of mirrored and log shipped database to another database for update
or insert operations?
Database snapshot can be used only for mirrored database but updates cannot be done. Also the secondary database of log shipping cannot used for database snapshot. Any ideas of how this can be implemented?
Thanks,
Preetha

Hmm in this case I think you need Merge Replication otherwise it breaks down the purpose of DR...again in that case..
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

BACKUP failed to complete the command BACKUP DATABASE. Check the backup application log for detailed messages.

Hi,
We have a back up that is failing.
The error is "BACKUP failed to complete the command BACKUP DATABASE RPS. Check the backup application log for detailed messages.".
As I understand it the backup application log is at C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG. From that all I get is
2014-03-05 14:49:29.41 Backup Error: 3041, Severity: 16, State: 1.
2014-03-05 14:49:29.41 Backup BACKUP failed to complete the command BACKUP DATABASE myDb. Check the backup application log for detailed messages.
The command I am using is
BACKUP DATABASE [MyDb]
TO DISK = N'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
WITH NOFORMAT, NOINIT, NAME = N'mydb-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
The database is Microsoft SQL Server Standard Edition (64-bit) Version 9.00.1399.06.
The computer is Windows server 2003 R2 Standard Edition SP2
The Db is 191 Gb and there is 227 Gb available on the D drive where it's being backed up to.
Any thoughts as to how I can track down the problem.
Is the 227Gb of spare disk space big enough to back up a 191 Gb database?
If not how much is needed?
Thanks

Hello,
Can you apply latest service pack .I dont know but guess that can be issue.Once faced ,not quite sure.Also can you just make your command like
BACKUP DATABASE [MyDb]
TO DISK = 'D:\Domains\SQL_Backup\DB\myDb\Mydb_FullBackup_20140305_1100.bak'
WITH NOFORMAT, NOINIT, STATS = 10
GO
Just a simple one .Is backup failing immediately or after some time .Error is not so helpful as it does not shows any information
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Backup Not Starting for 'Whole database offline + redo log backup' @ DB13

Hi Experts,
I am not able to perform 'Whole database offline + redo log backup' by DB13.
I have recently configured my 'init<SID>.sap' to take 'Whole database online + redo log backup' and its working perfectly fine.
I tried taking test backup for 'Whole database offline + redo log backup' but it didn't even started.
Thus I created another profile with name init<SID>back.sap and changed the Parameter
from 'backup_type = online' to 'backup_type = offline' and also tried by 'backup_type = offline_force'
rest all parameters being same as the profile init<SID>.sap
Kindly Suggest as I need to take set the backup Strategy as Mon-Fri -> 'Whole database offline + redo log backup' and Sat -> 'Whole database offline + redo log backup'
One more Query : While taking the redo log backup by DB13 why is it that some times it only saves the Files and some time it
saves and delete the files from the '/oracle/<SID>/oraarch' location. Please throw some light over this matter also.
Thanks,
Jitesh

Hi Mr Bhavik,
Thanks for your reply.. Here are the details you have asked for.
1.My SAP BASIS Patch Level is : 10. ( We shall be updating it by the end of this Year)
2. Br*tools version is :
BRTOOLS   7.00 (11)
kernel release    700
patch level   11
3. I don't have any file with name alert<dbsid>.log file (located at /oracle/<SID>/saptrace/background/) but i do have alert_<SID>.log
I execute the command more -p G alert_JMD.log
after my 'Whole database offline + redo log backup' again failed at DB13 but I was not able to see any specific complains while executing the above action.
I got the Error Detailed Log in DB13 as :
Detail log:                    beeneedv.aft
BR0051I BRBACKUP 7.00 (20)
BR0055I Start of database backup: beeneedv.aft 2010-11-08 13.16.43
BR0484I BRBACKUP log file: /oracle/JMD/sapbackup/beeneedv.aft
BR0280I BRBACKUP time stamp: 2010-11-08 13.16.43
BR0261E BRBACKUP cancelled by signal 13
BR0056I End of database backup: beeneedv.aft 2010-11-08 13.16.44
BR0280I BRBACKUP time stamp: 2010-11-08 13.16.45
BR0054I BRBACKUP terminated with errors
4. No I have not yet Tried 'execute such Offline+REdo log backups using brback command', will Try and post it Definately
5. Query : select grantee, granted_role from dba_role_privs;
result :
SQL> select grantee, granted_role from dba_role_privs;
GRANTEE                        GRANTED_ROLE
SYS                            SAPDBA
SYS                            EXP_FULL_DATABASE
SYS                            CONNECT
IMP_FULL_DATABASE              SELECT_CATALOG_ROLE
DBSNMP                         OEM_MONITOR
SAPSR3                         CONNECT
OPS$SAPSERVICEJMD              SAPDBA
SYS                            SELECT_CATALOG_ROLE
DBA                            DELETE_CATALOG_ROLE
DBA                            EXECUTE_CATALOG_ROLE
SYSTEM                         DBA
GRANTEE                        GRANTED_ROLE
OPS$ORAJMD                     SAPDBA
SAPDBA                         GATHER_SYSTEM_STATISTICS
SYS                            SCHEDULER_ADMIN
SYS                            AQ_USER_ROLE
SYS                            GATHER_SYSTEM_STATISTICS
SYS                            DELETE_CATALOG_ROLE
DBA                            GATHER_SYSTEM_STATISTICS
DBA                            IMP_FULL_DATABASE
EXECUTE_CATALOG_ROLE           HS_ADMIN_ROLE
IMP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
OPS$JMDADM                     CONNECT
GRANTEE                        GRANTED_ROLE
SYS                            LOGSTDBY_ADMINISTRATOR
SYS                            EXECUTE_CATALOG_ROLE
SYS                            RESOURCE
DBA                            SCHEDULER_ADMIN
DBA                            SELECT_CATALOG_ROLE
EXP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
SAPDBA                         SELECT_CATALOG_ROLE
SYS                            SAPCONN
SYS                            OEM_ADVISOR
SYS                            IMP_FULL_DATABASE
SELECT_CATALOG_ROLE            HS_ADMIN_ROLE
GRANTEE                        GRANTED_ROLE
OUTLN                          RESOURCE
LOGSTDBY_ADMINISTRATOR         RESOURCE
SAPSR3                         RESOURCE
OPS$SAPSERVICEJMD              RESOURCE
SYS                            RECOVERY_CATALOG_OWNER
DBA                            EXP_FULL_DATABASE
EXP_FULL_DATABASE              SELECT_CATALOG_ROLE
TSMSYS                         RESOURCE
OPS$ORAJMD                     RESOURCE
SAPCONN                        SELECT_CATALOG_ROLE
SYS                            OEM_MONITOR
GRANTEE                        GRANTED_ROLE
SYS                            AQ_ADMINISTRATOR_ROLE
SYS                            DBA
SYSTEM                         AQ_ADMINISTRATOR_ROLE
OPS$ORAJMD                     CONNECT
OPS$JMDADM                     SAPDBA
OPS$JMDADM                     RESOURCE
SAPSR3                         SAPCONN
SYS                            HS_ADMIN_ROLE
SYSTEM                         SAPDBA
OPS$SAPSERVICEJMD              CONNECT

Configuring Database for logging to citadel Database using shared variable engine

Hello All,
I have two systems with me here, one with LabVIEW 8.5 and one with LabVIEW 8.6, I'm using Shared Variables in my code and I am Logging to citadel Database. In a PC with LabVIEW 8.5, I am able to Log Data to citadel Database, but with the same code I am not able to Log Data from the PC with LabVIEW 8.6. Both the PC's have Database Installed and the connection with the Database Exists when I test connection with database through control panel. I would Like to know any configurations (in LabVIEW or in code or in Database or in PC) that have to be done for Logging to Database because the PC with LabVIEW 8.6 was added recently and the code was upgraded to 8.6.

It was due to a dll in LabVIEW, a dll named nitaglv.dll
Now I have a issue with Data Logging from the EXE, once the shared variables are deployed programatically from the EXE the Data Logging stops,
can I get any input on this issue..???

The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait

Every time I get this error, at different points of testing inserts and deletions on my table:
The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
Why do I keep getting this? All I'm doing is deleting several hundred thousand records and inserting them into a couple of tables. i shouldn't have to truncate my log every time or my application bombs out!
sys.databases only gives me this info for log_reuse_wait_desc which does nothing for me:
LOG_BACKUP

sp_helpdb BizTalkDTADb
ALTER DATABASE BiztalkDTADb
SET RECOVERY SIMPLE;
GO
DBCC SHRINKFILE (BiztalkDTADb_log, 1);
GO
sp_helpdb BizTalkDTADb
GO
ALTER DATABASE BiztalkDTADb
SET RECOVERY FULL
GO

Error connecting to planning database:Unsuccessful logon. Check log for det

Hello,
I am getting the following error which I am trying to connect to planning app data source for reports from workspace.
planning version is 9.3.1
can anyone suggest resolution for this?
Thanks
Hemanth
03-14 13:40:41 ERROR HrDsManagerBean     com.hyperion.reporting.util.HyperionReportException: Error connecting to database connection PLN: Unsuccessful logon. Check log for details.com.hyperion.planning.HspException
     at com.hyperion.reporting.connection.UserConnection.openConnection(Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)Lcom.hyperion.ap.IAPDomain;(Unknown Source)
     at com.hyperion.reporting.connection.UserConnection.openConnection()Lcom.hyperion.ap.IAPDomain;(Unknown Source)
     at com.hyperion.reporting.connection.UserConnection.<init>(Ljava.lang.String;Lcom.hyperion.reporting.security.IHsSession;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;ILjava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Z)V(Unknown Source)
     at com.hyperion.reporting.connection.ConnectionManager.getConnection(Lcom.hyperion.reporting.security.IHsSession;Lcom.hyperion.reporting.datasource.IHrDatasource;)Lcom.hyperion.reporting.connection.UserConnection;(Unknown Source)
     at com.hyperion.reporting.connection.ConnectionManager.getCube(Lcom.hyperion.reporting.security.IHsSession;Lcom.hyperion.reporting.datasource.IHrDatasource;Ljava.lang.String;)Lcom.hyperion.ap.IAPMdCube;(Unknown Source)
     at com.hyperion.reporting.connection.ConnectionManager.getCube(Lcom.hyperion.reporting.security.IHsSession;Ljava.lang.String;)Lcom.hyperion.ap.IAPMdCube;(Unknown Source)
     at com.hyperion.reporting.datasource.HrDsManagerBean.validateDatasource(Lcom.hyperion.reporting.datasource.IHrDatasource;)V(Unknown Source)
     at com.hyperion.reporting.datasource.HrDsManagerBean.doAddNew()Ljava.lang.String;(Unknown Source)
     at com.hyperion.reporting.datasource.HrDsManagerBean.process()Ljava.lang.String;(Unknown Source)
     at jsp_servlet._modules._com._hyperion._reporting._web._common.__hrdslogonfns._jspService(__hrdslogonfns.java:1470)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.hyperion.reporting.webviewer.HRSecurePagesFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.hyperion.reporting.webviewer.HRLocaleFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain;)V(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3151)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)

Database is up. All the services are running fine.
There are not changes in Servernames.
This error is occuring in all the environments. Dev, QA and Prod.

The transaction log for database 'BizTalkMsgBoxDb' is full.

Hi All,
We are getting the following error continously in the event viewer of our UAT servers. I checked the jobs and all the backup jobs were failing on the step to backup the transaction log file and were giving the same error. Our DBA's cleaned the message box manually and backed up the DB but still after some time the jobs starts failing and this error is logged in the event viewer.
The transaction log for database 'BizTalkMsgBoxDb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases".
Thanks,
Abdul Rafay
http://abdulrafaysbiztalk.wordpress.com/
Please mark this answer if it helps

Putting the database into simple recovery mode and shrinking the log file isn't going to help: it'll just grow again, it will probably fragment across the disk thereby impacting performance and, eventually, it will fill up again for the same reason
as before. Plus you put yourself in a very vulnerable position for disaster recovery if you change the recovery mode of the database: and that's before we've addressed the distributed transaction aspect of the BizTalkDatabases.
First, make sure you're backing up the log file using the BizTalk job Backup BizTalk Server (BizTalkMgmtDb). It might be that the log hasn't been backed up and is full of transactions: and, eventually, it will run out of space. Configuration
instructions at this link:
http://msdn.microsoft.com/en-us/library/aa546765(v=bts.70).aspx Your DBA needs to get the backup job running properly rather than panicking!
If this is running properly, and backing up (which was the case for me) and the log file is still full, run the following query:
SELECT Name, log_reuse_wait_desc
FROM sys.databases
This will tell you why the log file isn't properly clearing down and why it cannot use the space inside. When I had this issue, it was due to an active transaction.
I checked for open transactions on the server using this query:
SELECT
s_tst.[session_id],
s_es
.[login_name]
AS [Login Name],
DB_NAME
(s_tdt.database_id)
AS [Database],
s_tdt
.[database_transaction_begin_time]
AS [Begin Time],
s_tdt
.[database_transaction_log_record_count]
AS [Log Records],
s_tdt
.[database_transaction_log_bytes_used]
AS [Log Bytes],
s_tdt
.[database_transaction_log_bytes_reserved]
AS [Log Rsvd],
s_est
.[text]
AS [Last T-SQL Text],
s_eqp
.[query_plan]
AS [Last Plan]
FROM
sys.dm_tran_database_transactions
s_tdt
JOIN
sys.dm_tran_session_transactions
s_tst
ON s_tst.[transaction_id]
= s_tdt.[transaction_id]
JOIN
sys.[dm_exec_sessions]
s_es
ON s_es.[session_id]
= s_tst.[session_id]
JOIN
sys.dm_exec_connections
s_ec
ON s_ec.[session_id]
= s_tst.[session_id]
LEFT
OUTER
JOIN
sys.dm_exec_requests
s_er
ON s_er.[session_id]
= s_tst.[session_id]
CROSS
APPLY
sys.dm_exec_sql_text
(s_ec.[most_recent_sql_handle])
AS s_est
OUTER
APPLY
sys.dm_exec_query_plan
(s_er.[plan_handle])
AS s_eqp
ORDER
BY [Begin Time]
ASC;
GO
And this told me the spid of the process with an open transaction on BizTalkMsgBoxDB (in my case, this was something that had been open for several days). I killed the transaction using KILL spid, where spid is an integer. Then I ran the BizTalk
Database Backup job again, and the log file backed up and cleared properly.
Incidentally, just putting the database into simple transaction mode would have emptied the log file: giving it lots of space to fill up again. But it doesn't deal with the root cause: why the backups were failing in the first place.

Purging Logs for AS Database

Similar Messages

Maybe you are looking for