Log shipping: RESTORE LOG WITH CONTINUE_AFTER_ERROR?

Hi experts,
  I found the restore log on standby node failed with the error message like below. What happen? How do I prevent this error? How do I repair(rebuild a new log shipping DB)?
---  messages ---
Msg 4360, Level 16, State 1, Line 1
RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
--- errorlog ---
2014-07-16 07:00:00.42 Logon       Error: 18456, Severity: 14, State: 38.
2014-07-16 07:00:00.42 Logon       Login failed for user 'QCISAP\---'. Reason: Failed to open the explicitly specified database '---'. [CLIENT: <local machine>]
2014-07-16 07:01:49.52 spid60      Error: 4360, Severity: 16, State: 1.
2014-07-16 07:01:49.52 spid60      RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
2014-07-16 07:19:56.38 spid59      FlushCache: cleaned up 247385 bufs with 162904 writes in 278549 ms (avoided 0 new dirty bufs) for db 7:0
2014-07-16 07:19:56.38 spid59                  average throughput:   6.94 MB/sec, I/O saturation: 161105, context switches 305229
2014-07-16 07:19:56.38 spid59                  last target outstanding: 34, avgWriteLatency 35

One question, have you backup the log file with CONTINUE_AFTER_ERROR?
Have you seen in ERROR.LOG some info regarding the backup log which was forced by CONTINUE_AFTER_ERROR???
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

Similar Messages

  • Transaction log shipping restore with standby failed: log file corrupted

    Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
    Date                     
    9/10/2014 6:09:27 AM
    Log                        
    Job History (LSRestore_DATA_TPSSYS)
    Step ID                
    1
    Server                  
    DATADR
    Job Name                           
    LSRestore_DATA_TPSSYS
    Step Name                        
    Log shipping restore log job step.
    Duration                             
    00:00:03
    Sql Severity        0
    Sql Message ID 0
    Operator Emailed           
    Operator Net sent          
    Operator Paged               
    Retries Attempted         
    0
    Message
    2014-09-10 06:09:30.37  *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred while processing the log for database 'TPSSYS'. 
    If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
    Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Deleting old log backup files. Primary Database: 'TPSSYS'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.38  ----- END OF TRANSACTION LOG RESTORE    
    Exit Status: 1 (Error)

    I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in  that server with log shipping configuration
    error :
    Message
    2014-09-12 10:50:03.18    *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-12 10:50:03.18    *** Error: An error occurred while processing the log for database 'EAPDAT'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
    Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
    As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
    Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
    Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
    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 Articles

  • Restore Log with Standby Mode on VHDX disk problem - hotfix for SQL 2014 needed

    Restore Log with Standby Mode on Virtual VHDX disk cause a 9004 error in SQL Server 2014 ( test performed on Web edition and Standard version )
    Similar Bug for SQL 2008R2 is already registered with number hotfix
    KB2987585
    Restore operations always fail in Hyper-V R2 Server in situations ( text copied from
    KB2987585 page )
    The primary database has its transaction log file (.ldf) stored on a disk that has "Bytes per Physical Sector" set as 512 bytes.
    You take the transaction log backups of this database, and then you try to restore it by using the standby option on the secondary database.
    The secondary database transaction log file (.ldf) is located on a VHDX disk that has "Bytes per Physical Sector" set as 4,096 bytes.
    In this scenario, the restore operation fails and returns the following error message:
    Error: 9004, Severity: 16, State: 6.
    An error occurred while processing the log for database '<databasename>'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    After this error occurs, the secondary database goes into a suspect state.
    So restore from Generation1 to Generation2 machine ( where only VHDX disk is possible ) always fails and database is not accessible.
    Please create hotfix for SQL 2014 version

    Please create hotfix for SQL 2014 version
    This is a community forum, no one of use can create a hotfix for SQL Server.
    Raise a case at Microsoft Support or create an entry at MS Connect:
    http://connect.microsoft.com/SQLServer
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE

    제품 : RMAN
    작성날짜 : 2002-12-09
    RMAN9I HOW TO RESTORE ARCHIVE LOGS WITH LIMITED DISK SPACE
    ==========================================================
    PURPOSE
    이 자료는 Oracle 9.2 이상의 RMAN에서 사용 가능한 MAXSIZE 기능에 대하여
    설명할 것이다.
    How to restore archive logs with limited disk space
    Old Backup을 사용하여 RMAN으로 database를 recvoery할때, 모든 archived
    redo logfile들을 Restore할 destination의 disk space가 모자란 경우를 종종 만난다.
    이러한 경우 여러 개의 restore and recovery job으로 나누어 수행한다.
    즉, 첫 번째 restore and recovery job이 끝나면 archived redo logfile들을 지우고
    다음 적용될 것들을 restore한다. 그리고 다시 Recovery를 수행한다. 이러한 작업을
    원하는 시점까지 recovery를 하기위해 반복적으로 수행한다.
    Oracle 9iR2(9.2.0.x)부터 RMAN은 MAXSIZE option을 제공하는데 이것은 archive log
    file이 restore될 disk의 space를 control할 수 있게 해 준다.
    만약 disk space가 매우 제한적이라면, 즉 예를 들어 모든 archive log의 size 합보다
    disk free space가 적다면 MAXSIZE option을 사용하는 것은 매우 유용하다.
    이 OPTION이 기술되면 RMAN은 Media Manager에게 disk space 크기에 부합하는 만큼만
    archive log들을 restore하도록 한다. 부가적인 restore operation들은 restore된
    마지막 archive log가 적용될 때마다 발생한다.
    MAXSIZE option은 이러한 작업들을 하나의 rman job으로 처리하게 해 주고
    실수를 하지 않게 해 준다.
    아래는 MAXSIZE를 설명하기 위한 예제이며 총 6 단계로 구성되어 있다.
    STEP 1: Add data to the database to enforce log switches
    STEP 2: Backup the database and archive logs and delete the logs
    STEP 3: Add additional data to enforce new log switches
    STEP 4: Remove the data file and simulate a database crash
    STEP 5: Restore the data file from the backup
    STEP 6: Recover the database using MAXSIZE
    위 예제는 Unix와 Windows 모두에 적용될 수 있다.
    STEP 6 는 다음과 같은 조건으로 두 번 수행될 것이다.
    1) MAXSIZE가 archive log size보다 작은 경우:
    이 경우 RMAN-6558 Error message를 만나게 된다.
    그러므로 MAXSIZE를 archive log보다는 크게 설정해야한다.
    2) MAXSIZE가 archive log size보다 큰 경우:
    예를 들어 여러 개의 archive log를 포함할 수 있을 정도로 크게 설정하면
    restore/recovery는 user에게 transparent하게 수행되어진다.
    즉 archive log들은 restore된 후 applied되고 deleted되어 진다. 다시 새로운
    archive log들이 restore되어지고 applied된 후 deleted 되어 진다. 이러한 작업은
    recovery가 끝날 때까지 반복되어진다. 이러한 작업들이 진행되는 동안 RMAN은
    아무런 Message도 발생시키지 않는다.
    # Step 1: INSERT enough new data to generate log switches
    create table rman_tst (col1 varchar2 (10));
    begin
    for i in 1..30000 loop
    insert into rman_tst values(i,'test');
    commit;
    end loop;
    end;
    # Step 2: BACKUP the database and the archive logs automatically
    # and then delete the input
    run {
    backup database format='/web01/usupport/krosenme/admin/backups/db_%d%s%t'
    plus archivelog format='/web01/usupport/krosenme/admin/backups/arch_%d%s%t'
    delete input;
    # Step 3: INSERT enough new data to generate new log switches
    begin
    for i in 1..30000 loop
    insert into rman_tst values(i,'test');
    commit;
    end loop;
    end;
    # Step 4: REMOVE users01.dbf file and crash the database
    mv users01.dbf users01.org
    shutdown abort
    # Restore is now needed as the data file is deleted. The backup was
    # taken before the new data was added to it, thus archive logs are
    # needed to bring the database up to date
    # Step 5: RESTORE the data file from the full backup
    run {
    restore datafile '/web01/usupport/krosenme/oradata/kro_920/users01.dbf';
    # Step 6: RECOVER
    run {
    recover database delete archivelog maxsize 10 K;
    # This will fail with RMAN-6558 as the archived log has a size of 16 KB,
    # which is bigger than MAXSIZE limit of 10 KB. So the error is expected
    # and MAXSIZE works as designed.
    # Now rerunning STEP 6: but with MAXSIZE 50 K
    run {
    recover database delete archivelog maxsize 50 K;
    RELATED DOCUMENTS
    Recovery Manager Reference, Release 2 (9.2)

    cold backup means offline backup, you shut database normally and copy datafiles to another location.
    i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
    backing up archivelogs whith rman script which is:
    run {
    allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
    change archivelog all validate;
    sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
    release channel c1;
    so here is the details.
    1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
    2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
    So
    first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
    and then restore them and then apply them.
    we need rman commands to register these backups and restore them.
    Regards,
    Kamil

  • How to restore archive logs with rman

    Hi,
    here is the scenario:
    we have lost everything because of disk failure.
    we have a full cold backup and archivelog backups which were created after cold backup and were backed up with rman.
    after restoring from cold backup, because archivelog backups do not exist in controlfile, how can we catalog archivelog backups and restore them?
    could you give me the exact rman command for this?
    Best Regards,
    Kamil

    cold backup means offline backup, you shut database normally and copy datafiles to another location.
    i think operating system does not matter that much but it is RedHat Linux Enterprise Server.
    backing up archivelogs whith rman script which is:
    run {
    allocate channel c1 type disk format '$BKUPLOC/arch_%d_%u_%s_%p.bkp';
    change archivelog all validate;
    sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    backup archivelog time between 'SYSDATE - (30*60/(60*60*24))' and 'sysdate';
    release channel c1;
    so here is the details.
    1. because everything is lost, we restored all files(datafiles, controlfiles, redologs etc) from offline backup meaning copied all files from another location to corresponding location.
    2. want to apply archive logs which were created after cold backup till disk failure and we have these archive logs with backups which were taken by rman.
    So
    first of all, we want to register these archive log rman backups(because these backup information does not exist in restored controlfile)
    and then restore them and then apply them.
    we need rman commands to register these backups and restore them.
    Regards,
    Kamil

  • Hi, i got my 4s from my friend.... But when I'm trying to log with iCloud  I get an message like for this phone I can't use any new Apple ID ,... It's like the limit....

    Hi I'm trying to log with a new acc apple ... And in iCloud I'm getting every time an mess like the I already got the max limit of acc for this phone

    Sign in with the Apple ID that is already on the account.
    Disable Find My iPhone.
    Restore the device as new.
    Set up as you desire.

  • Open task sequence log with cmtrace on error

    Hi,
    Is there a way to make an SCCM 2012 R2 task sequence automatically open the smsts.log (with  cmtrace) when an error occurs?
    J.
    Jan Hoedt

    I would agree with Torstren. The difficult piece would be determining where the smsts.log is, based on where its at in the task sequence. Once you have that it wouldn't be too difficult to place those steps in the
    Gather Logs and StateStore on Failure group. The catch will be, even if CMTrace is open, the machine will still reboot after 15 minutes unless the cmd prompt is also open.

  • Can't update software because a message appears that I have to log with the same Apple ID that was used to purchase them: iMovie, Garage Band

    I can't update software because a message appears that I have to log with the same Apple ID that was used to purchase them: iMovie, Garage Band, iPhoto, but those apps came with OSX Lion.
    How can I get the "original" Apple ID?

    Support Downloads
    http://support.apple.com/downloads/
    Luckily, there is always more than one way to update software.

  • Error message when trying to log with more than a mobile account

    Hi guys,
    I face a very strange and worrying problem : when I log with a mobile account against my Snow Leopard Server, it works. But when I try to log with a second mobile using fast user switching, I have a strange error message saying that I can't connect with this user "at the moment". Once I log off from the first mobile account, I can log with the second one...
    It is as if it is not possible to have two or more mobile/network accounts logged simultaneously on the same client. Is this a known problem ?
    Thanks for your help,
    Eric.

    By design or not, this is a flaw, and a huge one ! I wanted to set up my home network so that each member of my family has a portable account. But this stupid design decision makes it impossible, since it makes impossible to have two or more users logged at the same time on a computer. So each time a member of my family wants to log on the family iMac, they have first to ask the previous logged member to log out !
    How is that not a flawed design ? I don't even see what are the pros of that design decision ?

  • Want to Generate custom logs with Log4J within Java Embedding activity

    Hi Gurus,
    i want to Generate custom logs with Log4J within Java Embedding activity. For that i have performed some steps, but the log file has not been created.
    ServerSide Configuration:
    *===============*
    1. I have copied the log4j-1.2.15.jar file to the "oracle.soa.ext_11.1.1" location and recreate the oracle.soa.ext.jar file using an-script, which appends the log4j.jar file to the classpath.( That was created successfully)
    2. Specify a File location in log4j.xml for creating the log file. (e.g. (<middleware_home>/config/customLog.log)
    3. Then create a folder and add log4j.xml and log4j.dtd file under the folder.
    4. Modify the startManagedWeblogicServer by adding JAVA_OPTIONS="-Dlog4j.configuration=<middleware_home>/config/log4j.debug.xml”
    5. Then restart the SOA server.
    log4j.xml :
    I have used fileAppender.
    DevelopmentSide Configuration:
    *===================*
    1. Create synchronous BPEL process and Add "JAVA Embedding Activity" inbetween receiveInput and replyOutput activity.
    2.Import the log4j-1.2.15.jar to the project libs
    3.In the BPEL source code, import the Logger class.
    4.Insert the code in the JAVA Embedding Activity
    Logger logger = Logger.getLogger("CustomLog");
    logger.info("CustomeLog " + getTitle());
    Compile and deploy the project into the SOA_server and test it. Test status is completed but log is not created in the mentioned location.
    Ref: http://blog.andrade.inf.br/search/label/Log4j
    Is there any other way to achieve this requirement. Please suggest.
    Thanks in Advance,
    Sharmistha

    You can try this.
    http://veejai24.blogspot.co.uk/2008/04/simple-way-to-implement-log4j-in-your.html
    Thanks,
    Vijay

  • Flashupdater filling system.log with spew

    Has anyone else noticed that flashupdater is filling their system.log with spew? This is happening on systems with and without flash installed. Sign, yet another blunder...

    Linc Davis wrote:
    That's the Flash updater included in Mac OS 10.7.4. It doesn't work on a case-sensitive boot volume, which is what you have.
    com.apple.flashupdat...: Apple Support Communities
    Correct. See this post: https://discussions.apple.com/thread/3952378?tstart=0
    and change your com.apple.flashupdater.plist file. That should take care of it.

  • Logging with whereabouts using open source and freeware

    You can find the html version of this at:
    http://www.acelet.com/whitepaper/loggingWithWhereabouts.html
    Logging with whereabouts using open source and freeware
    The purpose of logging is to find out what had happened when needed. When the
    time comes to read log messages, you want to know both the log message and its
    whereabouts (class name, method name, file name and line number). So you need
    to hard code whereabouts.
    But hard coded whereabouts are very difficult to maintain: when you modify your
    source code, line number changes; when you copy and paste a line, its class name
    and method name change. If whereabouts are wrong, you introduce bugs in your logging
    logic and the log messages are useless at the best.
    This article shows you an example of using freeware Redress tool to rectify whereabouts
    programmatically in your Makefile or Ant build file. So your whereabouts are always
    correct for both Java and JSP source file.
    Redress tool is part of SuperLogging at http://www.ACElet.com. SuperLogging also
    provides an open source wrapper Alog.java, which redirects log method calls to
    your favorite logging package. Redress tool can rectify whereabouts information
    on all Alog's method calls in your application. So, if you call Alog's log methods,
    these calls will be rectified by Redress.
    JDK 1.4 introduces a new utility package java.util.logging. The example in this
    article is based on JDK logging. Log4J is a cousin of JDK logging. Log4J users
    should have no difficulties to modify this example for Log4J. Both JDK logging
    and Log4J are excellent logging software for single JVM.
    Note: Redress tool rectifies method calls on Alog, not JDK logging. You need to
    call Alog instead of JDK logging in your application.
    Source code of Alog.java
    The following is the source code of Alog's JDK logging version. It serves as an
    library file and should be on your CLASSPATH:
    * Copyright Acelet Corp. 2000. All rights reserved
    * License agreement begins >>>>>>>>>> <br>
    * This program (com.acelet.opensource.logging.Alog) ("Software") is an
    * open source software. <p>
    * LICENSE GRANT. The Software is owned by Acelet Corporation ("Acelet").
    * The Software is licensed to you ("Licensee"). You are granted a
    * non-exclusive right to use, modify, distribute the Software for either
    * commercial or non-commercial use for free, as long as: <br>
    * 1. this copyright paragraph remains with this file. <br>
    * 2. this source code (this file) must be included with distributed
    * binary code.<br>
    * NO WARRANTY. This comes with absolutely no warranty. <p>
    * <<<<<<<<<< License agreement ends <p><p>
    * The purpose of releasing this open source program is to prevent vendor
    * lock in. <p>
    * You can code your program using this class to indirectly use Acelet
    * SuperLogging (com.acelet.logging). If later you want to swith to other
    * logging package, you do not need to modify your program. All you have
    * to do is: <p>
    * 1. modify this file to redirect to other logging packages. <br>
    * 2. replace existing com.acelet.opensource.Alog with your modified one. <br>
    * 3. you may have to reboot your EJB server to make the changes effect.<br>
    * <p>
    * This program is just a wrapper. For detail information about the methods
    * see documents of underline package, such as com.acelet.logging.Logging.
    * <p>
    * Visit http://www.ACElet.com for more information.
    * <p>
    * This file is a modified for using JDK logging as an EXAMPLE.
    * <br>
    * You can use Redress tool to keep your whereabouts information
    * always correct. See http://www.ACElet.com/freeware for detail.
    * <p>
    * Please see http://www/ACElet.com/opensource if you want to see the
    * original version.
    package com.acelet.opensource.logging;
    import java.util.logging.*;
    public final class Alog {
    * Log level value: something will prevent normal program execution.
    public static int SEVERE = 1000;
    * Log level value: something has potential problems.
    public static int WARNING = 900;
    * Log level value: for significant messages.
    public static int INFO = 800;
    * Log level value: for config information in debugging.
    public static int CONFIG = 700;
    * Log level value: for information such as recoverable failures.
    public static int FINE = 500;
    * Log level value: for information about entering or returning a
    * method, or throwing an exception.
    public static int FINER = 400;
    * Log level value: for detail tracing information.
    public static int FINEST = 300;
    static Logger logger;
    static {
    logger = Logger.getLogger("");
    public Alog() {
    public static void alert(String subject, String message) {
    public static void error(String text, int level, String fullClassName,
    String methodName, String baseFileName, int lineNumber) {
    String[] para = {lineNumber + "", baseFileName};
    logger.logp(getLevel(level), fullClassName, methodName, text, para);
    public static Level getLevel(int levelValue) {
    if (levelValue == SEVERE)
    return Level.SEVERE;
    else if (levelValue == WARNING)
    return Level.WARNING;
    else if (levelValue == INFO)
    return Level.INFO;
    else if (levelValue == CONFIG)
    return Level.CONFIG;
    else if (levelValue == FINE)
    return Level.FINE;
    else if (levelValue == FINER)
    return Level.FINER;
    else if (levelValue == FINEST)
    return Level.FINEST;
    else
    return Level.ALL;
    public static void log(String text, int level, String fullClassName,
    String methodName, String baseFileName, int lineNumber) {
    String[] para = {lineNumber + "", baseFileName};
    logger.logp(getLevel(level), fullClassName, methodName, text, para);
    public static void sendMail(String to, String from, String subject,
    String text) throws Exception {
    public static void sendMail(String to, String cc, String bcc, String from,
    String subject, String text) throws Exception {
    Test program
    The simple test program is Test.java:
    import com.acelet.opensource.logging.Alog;
    public class Test {
    public static void main(String argv[]){
    Alog.log("Holle world", Alog.SEVERE, "wrongClassName", "wrongMethod",
    "wrongFileName", -1);
    How to run the test program
    1. Compile Alog.java (JDK 1.4 or later, not before):
    javac Alog.java
    2. Download freeware Redress tool from http://ACElet.com/freeware.
    3. Run Redress tool:
    java -cp redress.jar Test.java
    4. Check Test.java. The Alog.log method call should be rectified.
    5. Run test program:
    java Test
    You should see log message with correct class name and method name.

    Hi;
      I found this code and would like to share it with you :
    JCoDestination destination = JCoDestinationManager
      .getDestination(DESTINATION_NAME2);
      JCoFunction function = destination.getRepository().getFunction(
      "RFC_FUNCTION_SEARCH");
      if (function == null)
      throw new RuntimeException("RFC_FUNCTION_SEARCH not found in SAP.");
      function.getImportParameterList().setValue("FUNCNAME", "*");
      function.getImportParameterList().setValue("GROUPNAME", "*");
      try {
      function.execute(destination);
      JCoTable funcDetailsTable = function.getTableParameterList()
      .getTable("FUNCTIONS");
      int totalNoFunc = funcDetailsTable.getNumRows();
      if (totalNoFunc > 0) {
      for (int i = 0; i < totalNoFunc; i++) {
      System.out.println("Function Name: "
      + funcDetailsTable.getValue(i));
      } catch (AbapException e) {
      System.out.println(e.toString());
      return;
      System.out.println("RFC_FUNCTION_SEARCH finished");
    It is working and retrieving FM.
    Regards
    Anis

  • Multi-task data logging with DAQmx

    I was wonder is it possible to use 'DAQmx Configure Logging' VI and 'DAQmx Start New File' VI for multiple tasks?  I'm doing synchronized high speed DAQ with NI PXI-6133 cards.  Each card (there are 16) must have its own task.  Although the DAQ is continuous, the user (software trigger) determines when data is saved to the disk and for how long.
    In my scenario the test length could be up to an hour with various test events scatter throughout.  The users want to display the data during the entire test length.  However they only want to write the data to disk during an event.  The event could last from 10 sec to 1 min.  That is why the users want to control when data is written to the disk.
    DAQmx Logging seems to work for a single task only, but I need to do multiple tasks.

    I've attempted to implement your suggestion, but I still do not acquire data for all channels for all tasks.  I've enclosed my VI.
    Attachments:
    TDMS Logging with Pause LoggingFSPR.vi ‏55 KB

  • Mail after interaction log with copied attachment

    Hello experts!
    I want to create a mail out of an interaction log with copied attachments.
    This means:
    1) I create an interaction log and add an attachment to it
    2) I select "more" "send mail"
    3) I want this mail to have the same attachment as the interaction log
    Does anybody know how to solve this?
    Greetings,
    littlesam
    EDIT: Right know I'm trying it with customizing, I created a BAPI, but I have no idea how to copy the attachments?
    Edited by: littlesam on Apr 15, 2010 1:47 PM

    Does anyone have a suggestion here?

  • Logging with Weblogic 10.3

    Hello,
    I am wondering how to manipulate the server logging with WebLogic 10.3. I get an error while deploying and I need further information for the packages concerning the named queries and for that I need to turn up the log level for this packages. Do I need to manipulate the config/logging.xml or which file?
    Thank you

    If you are deploying via the WebLogic admin console, here's the reference to configure logging level:
    Administration Console Online Help - [View and configure logs|http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/logging/ConfigureAndViewLogs.html]
    If deploying from command line, try including the -debug flag?
    (weblogic.Deployer Command-Line Reference - [Common Arguments|http://download.oracle.com/docs/cd/E12840_01/wls/docs103/deployment/wldeployer.html#wp1010461])

Maybe you are looking for