XI configuration parameter

Hi All,
I need to change XI configuration parameter LOCK_MESSAGE of category runtime to 0.
But i am not able to locate this parameter,can you please suggest how to change this parameter.
thanks and regads
Amit

Hi,
Are you not finding it here?
Log in to SAP PI -> Go to transaction SXMB_ADMIN -> Category (Runtime)-> click Configuration
Regards
Suraj
Edited by: S.R.Suraj on Sep 15, 2009 7:05 AM

Similar Messages

  • WDA application configuration parameter Stylesheet URI not working

    Hi Experts,
      I created an application configuration for a webdynpro ABAP application and populated theme path for parameter Stylesheet URI on application configuration. However when I execute the application using this application configuration, the application does not pick up the theme.
      If I pass the same path using URL parameter SAP-EP-THEMEROOT, it works. Also it works if I maintain it as URL parameter in SPRO
      However for my requirement I need it to work specifically from application / application configuration parameter. Has anyone faced this problem and found a solution?
    Thanks in Advance
    Tanmay

    I believe you need a redirect if you want to change between SSL and non-SSL.
    How about something in the line of (example with code 404):
    <If $code=404 && $security>
      Error fn="redirect" url="http://oursite/error.html"
    </If>.. where +$security+ means SSL.
    About the Error and URI, it seems uri="/error.html" would work, but it will not switch you from SSL to non-SSL.
    I'm curious why you would want to redirect a user to the non-SSL instance in this scenario..

  • Configuration parameter which are stored in automationBuild.xml file

    Do you know the correct path for below configuration parameter which are stored in automationBuild.xml file which is kept in src folder of osm project?
    <property name="studio.weblogic.home" value=""/>
         <property name="studio.java.sdk.home" value=""/>
         <property name="studio.osm.sdk.home" value=""/>

    Hi Sachin,
    Here is the info,
    studio.weblogic.home=<Weblogic_Installated Dir>/wlserver_10.3
    studio.java.sdk.home= <JDK Installed Dir> +(C:\jdk1.6.0_11, Something like this)+
    studio.osm.sdk.home=<OSM Installed Dir>/SDK
    Thanks,
    Naveen Jabade

  • Cannot configure parameter FORMULA_FILE_NO in task /CPMB/IOBJ_SOURCE_MD_CON

    Hi
    When I am trying load data from Bi infoobject to BPC dimension following error I am getting.
    "Cannot configure parameter FORMULA_FILE_NO in task /CPMB/IOBJ_SOURCE_MD_CONVERT"
    Can any body give me suggestion to resolve this issue
    Mahi

    Hi
    Here I  have taken  small exmaple
    I have taken city and country . country is attribute of city. I my transformation file id=id, city=0city, country=0country. No conversion file. I have validated transformation file successfully.  I hve created data manager  package. here I hve selected process chain i.e iobj_masterdata_load . I have not changed dynamic script. when running the package I am geting the above error
    thanks in advance
    mahi

  • CSCth95017 - Configurable parameter on how callingparty is displayed for hunt groups.

    Hello all,
    The "fixed-in" versions for this bug are listed below;
    Fixed in:                          (5)
    9.0(0.98000.74),9.0(0.98000.21),8.6(4.98000.21)
    8.6(2.21023.1),1.9(9.98000.16)
    But the bug is related to firmware and the "fixed-in" versions look like CUCM versions;
    Symptom:
    As of phone load 9.x and higher, calls to a hunt pilot show the following format for the calling party on the ringing phone.
    From 'Calling Party Name' for 'hunt pilot DN'
    i.e.  From John Doe for XXXX
    The previous format was
    From 'Calling Party Name' ('Calling Party Number')
    i.e.  From John Doe (XXX-XXX-XXXX)
    Need a configurable parameter to change the format to the previous format if the customer desires.
    Conditions:
    Occurs on phone loads 9.0(x) and above.
    Workaround:
    Downgrade to 8.4.x
    Can anyone clarify the "fixed-in" versions for this bug and where the versions are available for download.
    Cheers!
    Rob
    "Always movin' ahead and never lookin' back" - Springsteen

    Hi Rob,  The original documentation highlighted this as a phone issue. You have a good eye to catch this. The ultimate resolution was committed on the server side. I updated the bug Release-note to include more information about the fix. You will see that in Bug Toolking and Bug Search Tool in 24-48 hours.  Looks like it was necessary to change the information CUCM was sending out in order for the phones to leverage that information. Here is what I added to the bug: New Service Parameter :  "Display Hunt Pilot Name or DN for Hunt Group Calls When Alerting"  Default Value : True ? Default behavior will be new behavior from 8.x . For customers who want the previous behavior of  7.x  will have to set this parameter to false after upgrade.   Call Processing Fix from SCCP and SIP Side :   -       For Hunt Pilot calls, CUCM will not send Hunt Pilot URI to in outgoing INVITE when this service parameter is false but internally CUCM still treats this call as Hunt pilot call so that we do not break other features. -       For Hunt Pilot calls, CUCM will send the HP URI to phone when this SP is true.   For the versions above: 9.0(0.98000.74) - this is an internal nightly  build (.98xxx.). this *may* get it included in 9.0(1) 9.0(0.98000.21) - this is an internal nightly  build (.98xxx.). this *may* get it included in 9.0(1) 8.6(4.98000.21) - this is an internal nightly  build (.98xxx.). this *may* get it included in 8.6(5) 8.6(2.21023.1) - this gets it fixed in 8.6(2) engineering special branch commonly referred to as es23. TAC can provide this to you. This *may* get it included in the next 8.6.2su that gets posted to Cisco.com. 1.9(9.98000.16) - this appears to be a typo.  Regards, Wes

  • Configurable parameter of ccBPM for time out

    Hi,
    We are using ccBPM for collection files based on some correlation and we have set-up  a deadline branch for a particular time interval to collect files.
    We want to set the time out parameter as aconfigurable parameter so that everytime we dont need to touch ccBPM and can make changes in ID.
    i have tried using this but in deadline branch I can only define numeric value..
    Could you please tell me if we have any other way to implement this or we cannot use configurable parameter for deadline branch time duration?
    Thanks in Advance
    Best Regards,
    Harleen Kaur Chadha

    Hi Harleen Kaur Chadha,
    I understand your requirement is to collect messages for particular time period (like standard pattern BpmPatternCollectTime). And, if this time period changes, you want implement the changes without editing ccBPM.
    As far as I know, it is not possible. I do not recommend you to think about it, because, the time duration for which messages should be collected will not change every day in actual business scenario. I guess once you define time period based on business and technical details, it will be constant. Letu2019s say if it changes once in a blue moon, then edit the ccBPM. If you want more control on size of message getting collected you can combine these patterns [Link|http://help.sap.com/saphelp_nwpi711/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm ]
    Regards,
    Raghu_Vamsee
    Edited by: Raghu Vamsee on Jan 13, 2011 4:20 PM

  • MI - Configuration Parameter Sets

    When trying to access the "Configuration Parameter Sets" option under the Mobile Administrator page I am getting an error:
    Connection is already closed and no longer associated with a managed connection
    When I try to create a new parameter set I get a java.lang.NullPointerException  exception. Please help.
    Thanks,
    Mahwish

    Hi,
       If you click on any link under the mobile Administrator you will get similar error like "Connection is already closed and no longer associated with a managed connection"
         For this above issue please check the following points.
    1. Visual Admin>Services>Connection Container.. here Check the number of connections values?? 
    2. Check all the authorization are assigned to access the RFCs to user which is mentioned in SAPJRAFactory_EN.
       If we resolve the above problem you would not get any null pointerException during creation of the parameter sets.
    Regards,
    Anil Kumar.

  • HOWTO configure parameter options in oracle apps R11i for reports ??

    Hello
    I've developed a character report with orientation = landscape ,width=180 and height=66 on my laptop.It takes FROM DATE & TO DATE input from user which are passed to the sql query.
    KINDLY GUIDE ME IN CONFIGURING PARAMETERS OPTIONS TO RUN THIS REPORT IN ORACLE APPLICATIONS 11i.
    More what would the Token Option be in my case.
    I'm pasting the sql query and the last line indicated in bold takes parameter.I'm working in the HR & PAYROLL SCHEMA.
    SELECT DISTINCT
    PAPF.PERSON_ID AS "PERSON_ID",
         PAPF.BUSINESS_GROUP_ID,
    PAPF.TITLE,
         PAPF.FIRST_NAME,
         PAPF.MIDDLE_NAMES,
         PAPF.LAST_NAME,
    PGD.SEGMENT4 AS "GRADE",
         PPG.SEGMENT1 AS "GROUP_NAME",
    PPG.SEGMENT2 AS "DEPARTMENT",
    PPEMP.PEM_ATTRIBUTE8 AS "PREVIOUS_SALARY",
    PAC.SEGMENT2 AS "SALARY_OFFERED",
    PQFS.TITLE AS "QUALIFICATIONS",
         (SELECT
         SUM(PPEMP.PEM_INFORMATION1)
              FROM
              PER_PREVIOUS_EMPLOYERS PPEMP
              WHERE
              PPEMP.PERSON_ID=PAPF.PERSON_ID
              AND PPEMP.BUSINESS_GROUP_ID=3788
              ) AS "RELEVANT_EXPERIENCE",
              (SELECT
              SUM(PPEMP.PERIOD_YEARS) ||' '||'Y'||' '|| SUM(PPEMP.PERIOD_MONTHS)||' '||'M'          
              FROM
              PER_PREVIOUS_EMPLOYERS PPEMP
              WHERE
              PPEMP.PERSON_ID=PAPF.PERSON_ID
              AND PPEMP.BUSINESS_GROUP_ID=3788
              ) AS "TOTAL_EXPERIENCE",
              (SELECT PJD.SEGMENT4
                   FROM                
                                  PER_JOBS PJ,
                                  PER_JOB_DEFINITIONS PJD
    WHERE                         PAPF.PERSON_ID=PAAF.PERSON_ID
    AND                              PAAF.JOB_ID=PJ.JOB_ID                          
    AND                          PJ.JOB_DEFINITION_ID = PJD.JOB_DEFINITION_ID
    AND                          PJ.BUSINESS_GROUP_ID = 3788) AS "FUNCTIONAL_TITLE"
    FROM
    PER_ALL_PEOPLE_F PAPF,
    PER_ALL_ASSIGNMENTS_F PAAF,
         PER_JOBS PJ,
         PER_JOB_DEFINITIONS PJD,
    PAY_PEOPLE_GROUPS PPG,
    PER_GRADES PG,
         PER_GRADE_DEFINITIONS PGD,
    PER_QUALIFICATIONS PQFS,
    PER_PREVIOUS_EMPLOYERS PPEMP,      
    HR_ALL_ORGANIZATION_UNITS HRAOU,
         PER_PERSON_ANALYSES PPALYS,
         PER_ANALYSIS_CRITERIA PAC,
         APPS.FND_ID_FLEX_STRUCTURES FIFS,
         HR_LOCATIONS_ALL HLA,
         PER_APPLICATIONS PA
    WHERE PAPF.PERSON_ID = PAAF.PERSON_ID
    AND PAAF.GRADE_ID = PG.GRADE_ID
    AND PG.GRADE_DEFINITION_ID = PGD.GRADE_DEFINITION_ID
    AND PAAF.PEOPLE_GROUP_ID = PPG.PEOPLE_GROUP_ID
    AND     PAAF.JOB_ID (+)=PJ.JOB_ID
    AND PJ.JOB_DEFINITION_ID (+)=PJD.JOB_DEFINITION_ID
    AND PQFS.PERSON_ID (+)= PAPF.PERSON_ID
    AND PPEMP.PERSON_ID (+)= PAPF.PERSON_ID
    AND HRAOU.ORGANIZATION_ID (+)= PAAF.ORGANIZATION_ID
    AND PAPF.BUSINESS_GROUP_ID=3788
    AND PAPF.EFFECTIVE_END_DATE=TO_DATE('31/12/4712','DD/MM/RRRR')
    AND PAAF.EFFECTIVE_END_DATE=TO_DATE('31/12/4712','DD/MM/RRRR')
    AND PAPF.CURRENT_APPLICANT_FLAG='Y'
    AND PAAF.ASSIGNMENT_TYPE='A'
    --AND    HRAOU.ORGANIZATION_ID = PAAF.ORGANIZATION_ID
    AND nvl(PPEMP.END_DATE,TO_DATE('31/12/4712','DD/MM/RRRR'))=nvl((SELECT MAX(END_DATE)
    FROM PER_PREVIOUS_EMPLOYERS P
              WHERE PPEMP.PERSON_ID=P.PERSON_ID),TO_DATE('31/12/4712','DD/MM/RRRR'))
    AND PAPF.PERSON_ID=PPALYS.PERSON_ID
    AND PPALYS.ANALYSIS_CRITERIA_ID=PAC.ANALYSIS_CRITERIA_ID
    AND FIFS.ID_FLEX_NUM=PAC.ID_FLEX_NUM
    AND FIFS.STRUCTURE_VIEW_NAME='HIRING APPROVAL'
    AND HLA.LOCATION_ID=PAAF.LOCATION_ID
    AND PA.PERSON_ID=PAAF.PERSON_ID
    AND PAPF.EFFECTIVE_START_DATE between :From_Date And :To_Date

    Hi Dinesh
    I have some bad news for you I'm afraid. Discoverer workbooks are not stored as SQL definitions, they are stored as BLOBs within the database. It is therefore not possibly to write any sort of query to interrogate the inner workings of a workbook. The only way to do this is to open each workbook in turn and analyze it.
    Sorry to be the bringer of bad news
    Best wishes
    Michael

  • RAR: Configuration parameter "Report directory on the SAP ERP Server"

    Hi,
    Under a scenario with a standalone SAP GRC AC 5.3 installation and connected with several R/3 system through JCO destinations.
    Which SAP ERP Server Directory do we have to specify?
    Many thanks in advance. Best regards,
      Imanol

    Sunny,
    I did not mean the Spool File Directory.
    I mean the parameter "SAP Server Application Location". The parameter above FTP Location.
    Under the configuration guide it is said for this parameter that:
    "The report directory on the SAP Enterprise Resource Planning (ERP) application servers. This is the temporary storage location for security reports generated by background jobs. Virtual directories delivered in the ERP system, such as DIR_HOME and DIR_TMP, are supported. These directories are viewed with SAP ERP transaction, AL11. The same directory name is used for all SAP back-end systems."
    Thanks in advance. Best regards,
      Imanol

  • Configuring parameter fields in Search Bar pattern UI configuration

    Hello all,
    Im configuring a search bar UI pattern for an entity service and have some doubts. The parameter fields description seems to be the entity service field description.
    - Is there a way to internationalize this field descriptions ?
    - The search bar always generate a button called "Go". Is it possible to change the button text ?
    Thanks in advance,
    Helder Ribeiro

    Thanks Abdul, but where in CAF Runtime configurator?
    Regarding the recommendation of custom WDP or VC app: Under what circumstance would one use the UI patterns.  Again our desire is to find the limit of configuring UI patterns vs. custom UIs.

  • Cannot update Pcd Configuration parameter Pcd.Xfs.Cache.HardReferenceLimit

    NW 7.0 sp15
    I am trying to update the pcd configuration file pcdStartup.properties. I want to increase the parameter  Pcd.Xfs.Cache.HardReferenceLimit from the default value of 100 to 500 as recamended by SAP.
    I have updated the file, and then loaded the configuration into the Portal using the Support desk --> pcd Configuration --> Reload. I have also started and stopped the SAP instance. Still no chnages in my pcd configuration. Pcd parameter Pcd.Pl.WriteProtectActivated=false
    Any help would be appreciated.
    Thank you,
    Sarah

    I have read that link and the SAP documentation on pcd parameters,
    I am not trying to set the parameter pcd property  Pcd.Pl.WriteProtectActivated , I am trying to set the pcd parameter Pcd.Xfs.Cache.HardReferenceLimit from the default value of 100 to 500.
    I am not sure about the process since it does not seem to work. I have changed the pcd file  file pcdStartup.properties and loaded it via the Portal Support and I have rebooted the sap instance. The file has the new value in it but it does not change the configuration value.
    Thanks
    Sarah

  • File adapter configuration parameter for "hexadecimal conversion"

    (File adapter for XI 2.0)
    Does anybody know the exact File adapter configuration parameters for reading a file with hexadecimal control characters as seperators. My file has
    3 types of seperators - i.e "2F", "05" & "0D2F"
    Eg: xml.fieldSeparator= "2F"
    When I specify this the file is getting split into fields
    at all the seperators in the file. I guess I am not using the right format in my defination ?
    Dorai

    Is there any special format for reading a file containing hexadecimal control characters?
    The file to be processed has hexadecimal separators:
    Field Delimiter        : '09' or '05'
    End of record delimiter: '0A' or '25'
    End of Table delimiter : '07' or '2F'
    Initially i would like to read the file into XI as it is i.e without any split by using "xml.fieldFixedLengths= "
    However, everytime I process the file(with hexadecimal contol characters), I have noticed that my file is getting split, even when I did not specify anything for field separator(i.e when i used fixed field length).
    Thanks,
    Dorai

  • Configuring "Scan To E-mail" on HP Officejet Pro 8600 Plus N911g

    This is the same issue reported by several other users in this forum to which no solution has been provided.
    I have been unsuccessful in setting up the scan to e-mail option for a HP Officejet Pro 8600 Plus N911g purchased on August 12th 2012 and using the firmware CLP1CN1150CR.
    I am trying to do this through the Embedded Web Server interface to the printer from an iMac running Mac OS X 10.6.8 and HP Utility 5.8.0.  More specifically the page under "Scan -> Scan to E-mail -> Outgoing E-mail Profiles".
    I have tried 2 different SMTP outgoing servers, each of which works well to send e-mail from the computer: Apple iCloud e-mail service (formerly known as Mobile Me, formerly known as .Mac) and AT&T Net e-mail service.  I verified that the server name, port number and authentication login/password values were all correct.
    When scan to e-mail is used from the printer, I get an error message:  Cannot connect to server.  Check server name and address.
    When tested from the computer during the setup of an outgoing e-mail profile, I get an error message:  The device could not send the test e-mail message. (EmailAccounts-timeout).
    When I try to configure the page under "Settings -> E-mail Alerts -> E-mail Server" and use exactly the same values as the ones in the outgoing e-mail profile above, the Save and Test option fails with an error message:  The device could not send the test e-mail message.
    Interestingly enough, I am able to use the computer's e-mail client with the option Scan To Computer -> E-mail as PDF or E-mail as JPEG.  With this option, the file is scanned and added as an attachment to a mail message from the Mail client under Mac OS X.  When I press the Send button, the e-mail is sent successfully through the same SMTP server.
    All the error messages seem to indicate that the printer's e-mail client software is unable to establish a connection to the SMTP server.  However, it is not clear what configuration parameter is the one that could be causing the problem.
    This question was solved.
    View Solution.

    After further research, I noticed that there are other possible default Simple Mail Transfer Protocol (SMTP) port values:
    Port 25 is the standard SMTP port number.
    Port 465 is the port number for SMTP over SSL, Secure SMTP (SSMTP).
    Port 587 is the dedicated port number for a Mail Submission Agent (MSA) that uses a variant of the SMTP, as specified in RFC 6409, which requires that clients are authorized and authenticated to use the mail submission service.
    I had been using port  number 25 as this is the standard one.  However, all tests were failing.  Hence, I decided to try the tests with ports numbers 465 and 587.
    Port number 465 failed with the same errors listed above.  However, the tests passed with port number 587.  After saving the successful configuration with port number 587, I tried the scan to e-mail option from the printer and it worked.
    A mail submission agent (MSA) is a computer program or software agent that receives electronic mail messages from a mail user agent (MUA) and cooperates with a mail transfer agent (MTA) for delivery of the mail.
    Historically in Internet mail, both MTA and MSA functions use port number 25.  However, many Internet Service Providers (ISPs)  and enterprise or institutional networks restrict the ability to connect to remote MTAs on port 25.
    With a dedicated port 587, it is always possible for users to connect to their domain to submit new mail.  Availability of a MSA on port 587 enables nomadic users to continue to send mail via their preferred submission servers even from within others' networks.  Using a specific submission server is a requirement when sender policies or signing practices are enforced.
    I know that many users may find the technical details boring or confusing, but I just wanted to include some background to those who actually care about this level of detail.  I also wanted to provide a possible solution to other users who are experiencing the same problem.
    So, in a nutshell, if the Scan To E-mail option is not working for you using port number 25, then try one of the other SMTP port numbers listed above.  If none of them work, check your mail provider for other possible outgoing server port numbers.

  • NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A

    제품 : SQL*NET
    작성날짜 : 2002-05-07
    NET8의 LOGGING과 TRACE 관련 PARAMETER에 대한 Q & A
    =================================================
    PURPOSE
    Net8을 이용하면서 발생하는 문제를 추적 하기위해 oracle의 configuration
    file에 들어갈 수 있는 parameter와 logging과 tracing을 하는 방법에 대해
    질의/응답을 통해 알아 보도록 한다.
    Explanation
    1) NET8에서 trace를 사용하는 이유와 어떤 component들에 trace를 할 수 있나?
    Trace의 특징은 네트워크을 수행하게 될때 network event들을 기술한다
    즉 trace와 관련된 일련의 문장들이 자세하게 생성된다.
    "Tracing"의 운영으로 log파일에 제공되어 있는 것 보다 NET8의 component들의
    내부적인 정보를 보다 많이 얻을 수 있다.
    이러한 정보는 에러의 결과로 인하여 발생하는 동일한 event들로 파일들에
    결과가 생성되어 이를 이용하여 문제의 원인을 판단할 수 있다.
    주의 : trace의 기능을 이용하는 경우 충분한 disk space와 system performance의
    현격한 저하를 가져올 수 있다 즉 trace의 기능은 반드시 필요할
    경우에만 사용할 것을 권한다.
    << trace의 기능을 이용하여 trace를 할 수 있는 component들 >>
    * Network listener
    * Net8 components on the client and server
    * Connection Manager
    * Oracle Names Server
    * Oracle Names Control Utility
    * TNSPING utility
    2) 어떤 parameter들을 설정하면 trace 기능을 이용할 수 있는가 ?
    tracing을 하기 위해서는 특정 trace parameter들을 설정함으로써 가능하며
    아래에 주어진 방법들과 또는 utility들중 하나를 선택하여 설정함으로써
    사용할 수 있다.
    * Component Configuration Files
    * Component Control Utilities
    * Oracle Trace
    component의 configuration 파일을 이용하여 traceing parameter를 설정하려면
    1.component의 configuration 파일에 다음의 traceing parameter를 설정한다.
    - SQLNET.ORA for client or server, LISTENER.ORA for listener:
    TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
    TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    2.만일 component들이 수행중인 동안 configuration 파일의 수정이 있었다면
    병경된 parameter들을 사용하기 위해 component들을 다시 시작하여야 한다.
    component control utility들을 이용하여 trace parameter들을 설정하려면
    1. listener의 경우, Listener Control Utility(lsnrctl)에서 TRACE 명령어를
    이용하여 listener가 수행중인 동안에도 trace level을 설정할 수 있다.
    EX)
         RC80:/mnt3/rctest80> lsnrctl
         LSNRCTL for SVR4: Version 8.0.4.0.0 - Production on 01-SEP-98 15:16:52
         (c) Copyright 1997 Oracle Corporation. All rights reserved.
         Welcome to LSNRCTL, type "help" for information.
         LSNRCTL> trace admin
         Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
         Opened trace file: /mnt4/coe/app/oracle/product/8.0.4/network/trace/
    lsnr_coe.trc
         The command completed successfully
         LSNRCTL> trace off
         Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
         The command completed successfully
         LSNRCTL> exit
         RC80:/mnt3/rctest80>
    2. Oracle Names의 경우, Names Control Utility(namesctl)에서 TRACE_LEVEL
    명령어를 이용하여 Oracle Names가 수행중인 동안에도 trace level을
    설정할 수 있다.
    주의 : Connection Manager의 경우, trace level은 configuration 파일인 CMAN.ORA
    에서만 설정할 수 있다.
    Oracle Enterprose manager(이하 OEM)에 있는 Oracle Trace는 trace parameter들을
    설정하고 GUI를 통해 trace data의 형태를 볼수 있도록 하는 tracing tool이다.
    3) trace된 data를 해석할 수 있는 다른 utility들이 있다면 ?
    Trace Assistant를 사용하면 사용자의 *.trc 파일 (SQL*Net v2의 형식에 의해
    생성된) 또는 *.txt (Orace Trace 과 TRCFMT에 의해 생성된 출력물)을 통해
    trac된 정보를 해석할 수 있다.
    이 유틸리티 네트워크의 문제들로 인해 발생하는 문제점들을 진단하고
    해결하는 데 보다 많은 정보를 제공하여 사용자의 이해를 돕는다.
    * the source and destination of trace files
    * the flow of packets between network nodes
    * which component of Net8 is failing
    * pertinent error codes
    다음에 주어진 명령어를 수행하므로써 Trace Assistant 실행할 수 있다.
    trcasst [options] <filename>
    Trace Assistant Text Formatting Options
    -o Displays connectivity and Two Task Common (TTC) information.
    After the -o the following options may be used:
    c (for summary connectivity information)
    d (for detailed connectivity information)
    u (for summary TTC information)
    t (for detailed TTC information)
    q (displays SQL commands enhancing summary TTC information)
    -p Oracle Internal Use Only
    -s Displays statistical information
    -e Enables display of error information After the -e, zero
    or one error decoding level may follow:
    0 or nothing : translates the NS error numbers dumped from the
    nserror function plus lists all other errors
    1 : displays only the NS error translation from the nserror function
    2 : displays error numbers without translation
    만일 option들이 제공되지 않는다면 기본적으로 -odt -e -s가 지정되어 자세한
    connectivity, Two-Task Common, 에러 level 0 그리고 통계정보들이 tracing 된다.
    4) SQL*Net v2 tracing과 어떻게 다른가 ?
    Net8 tracing에서는 이전 버전인 SQL*NET V2에서 제공 되는 모든 option을
    포함하고 있고 Oracle Trace의 기능이 추가되었다.
    이것은 Oracle Trace Repository를 OEM 콘솔을 통하여 사용자의 trace 정보를
    관리할 수 있도록 허용한다.
    5) *.cdf와 *.dat은 어떤 파일 인가 ?
    *.cdf 와 *.dat 파일들은 Oracle Trace에 의해 생성되는 파일들로서 이 파일들을
    읽기 위해서는 반드시 trcfmt utility를 이용해야만 한다.
    trcfmt는 binary (*.dat와 *.cdf의 확장자) 파일내에 있는 data를
    일반 text(.txt의 확장자)로 정보를 추출한다. 이 tool을 사용하기 위해서는
    다음의 명령어를 이용하면 된다.
    trcfmt collection.cdf
    주의 : .cdf와 .dat파일이 존재하는 디렉토리가 아닌 곳에서 이 tool을 이용
         한다면 path가 포함되야 한다. 만일 하나의 .cdf 와 .dat 파일들내에
         여러 프로세스들의 tracing정보가 수집된다면 그것들은 process_id.txt의
    이름과 함께 파일이 추출될 것이다.
    6) trac관련 configuration은 어떤 것이 있으며 설정할 수 있는 parameter는
    무엇이 있는가 ?
    ==========================================================================
    || SQLNET.ORA Parameters ||
    ==========================================================================
    DAEMON.TRACE_DIRECTORY
    Purpose: Controls the destination directory of the Oracle
    Enterprise Manager daemon trace file
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_DIRECTORY=/oracle/traces
    DAEMON.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level for
    the Oracle Enterprise Manager daemon.
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_LEVEL=10
    DAEMON.TRACE_MASK
    Purpose: Specifies that only the Oracle Enterprise Manager daemon
    trace entries are logged into the trace file.
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_MASK=(106)
    LOG_DIRECTORY_CLIENT
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_CLIENT=/oracle/network/trace
    LOG_DIRECTORY_SERVER
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Valid in File: SQLNET.ORA
    Example: LOG_DIRECTORY_SERVER=/oracle/network/trace
    LOG_FILE_CLIENT
    Purpose: Controls the log output filename for an Oracle client.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_CLIENT=client
    LOG_FILE_SERVER
    Purpose: Controls the log output filename for an Oracle server.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_SERVER=svr
    NAMESCTL.TRACE_LEVEL
    Purpose: Indicates the level at which the NAMESCTL program should
    be traced.
    Default Value: OFF
    Values: OFF, USER, or ADMIN
    Example: NAMESCTL.TRACE_LEVEL=ADMIN
    NAMESCTL.TRACE_FILE
    Purpose: Indicates the file in which the NAMESCTL trace output is
    placed.
    Default Value: namesctl_PID.cdf and namesctl_PID.dat
    Example: NAMESCTL.TRACE_FILE=NMSCTL
    NAMESCTL.TRACE_DIRECTORY
    Purpose: Indicates the directory where trace output from the NAMESCTL
    utility is placed.
    Default
    Value: $ORACLE_HOME/network/trace
    Example: NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
    NAMESCTL.TRACE_UNIQUE
    Indicates whether a process identifier is appended to the
    Purpose: name of each trace file generated, so that several can
    coexist.
    Default
    Value: OFF
    Values: OFF or ON
    Example: NAMESCTL.TRACE_UNIQUE = ON
    TNSPING.TRACE_DIRECTORY
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TNSPING.TRACE_DIRECTORY=/oracle/traces
    TNSPING.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TNSPING.TRACE_LEVEL=10
    TRACE_DIRECTORY_CLIENT
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_CLIENT=/oracle/traces
    TRACE_DIRECTORY_SERVER
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_SERVER=/oracle/traces
    TRACE_FILE_CLIENT
    Purpose: Controls the name of the client trace file
    Default Value: SQLNET.CDF and SQLNET.DAT
    Example: TRACE_FILE_CLIENT=cli
    TRACE_FILE_SERVER
    Purpose: Controls the name of the server trace file
    Default Value: SVR_PID.CDF and SVR_PID.DAT
    Example: TRACE_FILE_SERVER=svr
    TRACE_LEVEL_CLIENT
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_CLIENT=10
    TRACE_LEVEL_SERVER
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_SERVER=10
    TRACE_UNIQUE_CLIENT
    Used to make each client trace file have a unique name to
    Purpose: prevent each trace file from being overwritten with the next
    occurrence of the client. The PID is attached to the end of
    the filename.
    Default
    Value: OFF
    Example: TRACE_UNIQUE_CLIENT=ON
    USE_CMAN
    If the session is in an Enhanced Discovery Network with a
    Purpose: Names Server, this parameter forces all sessions to go
    through a Connection Manager to get to the server.
    Default
    Value: FALSE
    Values: TRUE or FALSE
    Example: USE_CMAN=TRUE
    ==========================================================================
    || LISTENER.ORA Parameters ||
    ==========================================================================
    LOG_DIRECTORY_listener_name
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_LISTENER=/oracle/traces
    LOG_FILE_listener_name
    Purpose: Specifies the filename where the log information is
    written
    Default Value: listener_name.log
    Example: LOG_FILE_LISTENER=lsnr
    TRACE_DIRECTORY_listener_name
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_LISTENER=/oracle/traces
    TRACE_FILE_listener_name
    Purpose: Controls the name of the listener trace file
    Default Value: LISTENER_NAME.CDF and LISTENER_NAME.DAT
    Example: TRACE_FILE_LISTENER=lsnr
    TRACE_LEVEL_listener_name
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 - WorldWide Customer Support trace information
    Example: TRACE_LEVEL_LISTENER=10
    ==========================================================================
    || NAMES.ORA Parameters ||
    ==========================================================================
    NAMES.TRACE_DIRECTORY
    Purpose: Indicates the name of the directory to which trace files
    from a Names Server trace session are written.
    Default
    Value: platform specific
    Example: names.trace_directory = complete_directory_name
    NAMES.TRACE_FILE
    Purpose: Indicates the name of the output file from a Names Server
    trace session. The filename extension is always.trc
    Default
    Value: names
    Example: names.trace_file = filename
    NAMES.TRACE_LEVEL
    Purpose: Indicates the level at which the Names Server is to be
    traced.
    Default Value: OFF
    Example: names.trace_level = OFF
    NAMES.TRACE_UNIQUE
    indicates whether each trace file has a unique name, allowing
    Purpose: multiple trace files to coexist. If the value is set to ON, a
    process identifier is appended to the name of each trace file
    generated.
    Default
    Value: OFF
    Example: names.trace_unique = ON
    names.trace_file = names_05.trc
    ==========================================================================
    CMAN.ORA Parameters
    ==========================================================================
    TRACING
    Default
    Value: NO
    Example: TRACING = NO
    References
    7) listener.log 파일에 loggin정보를 남기지 않게 하는 방법이 있나요 ?
    고객이 개발하여 사용중인 application에서 NET8을 이용하여 접속하거나 접속을
    종료하는 경우 listener.log에 이와 관련된 정보가 남으며, 수 많흔 사용자가
    접속을 하게되므로서 급속하게 listener.log 파일이 커져 file system이 꽉
    차거나 데이터베이스가 hang이 되는 결과를 초래하는 경우가 있다.
    고객들은 listener.log에 write할수 있는 메세지의 양에 제한을 두기를 원하는
    경우가 있으나 이러한 기능은 제공되지 않는다. 하지만 listener의 logging은
    on 또는 off를 할 수는 있다.
    Net8에서는 listener.ora에 "LOGGING_(the listener name)=off"를 설정하게 되면
    listener의 logging을 멈출 수 있다.
    ** SQL*NET 2.3.x 에서도 이 parameter가 유효한가요 ? **
    물론 사용이 가능합니다. NET8에서 사용하는 것과 동일하게 parameter를
    listener.ora에 설정함으로서 가능합니다.
    EX)
    LOGGING_LISTENER=OFF
    이 parameter는 listener의 전체 logging을 disable하는 parameter로 일부만
    여과하여 logging할 수 있는 기능은 아니다.
    이 parameter는 NET8에 알려진 parameter로 SQL*NET 2.3.x manuals에 나와
    있지는 않지만 정상적으로 사용할 수 있다.
    Reference Ducumment
    ---------------------

  • NET8의 LOGGING AND TRACE관련 PARAMETER에 대한 Q & A

    제품 : SQL*NET
    작성날짜 : 1999-07-30
    NET8의 LOGGING AND TRACE관련 PARAMETER에 대한 Q & A
    ==================================================
    PURPOSE
    NET8의 LOGGING AND TRACE관련 PARAMETER에 대해 알아 보도록한다
    Explanation
    1. NET8에서 trace를 왜 사용하고 어떤 component들에 trace를 할 수 있나요 ?
    Trace의 특징은 네트워크을 수행하게 될때 network event들을 기술한다
    즉 trace와 관련된 일련의 문장들이 자세하게 생성된다.
    "Tracing"의 운영으로 log파일에 제공되어 있는 것 보다 NET8의 component들의
    내부적인 정보를 보다 많이 얻을 수 있다.
    이러한 정보는 에러의 결과로 인하여 발생하는 동일한 event들로 파일들에
    결과가 생성되어 이를 이용하여 문제의 원인을 판단할 수 있다.
    주의 : trace의 기능을 이용하는 경우 충분한 disk space와 system
    performance의 현격한 저하를 가져올 수 있다.
    즉 trace의 기능은 반드시 필요할 경우에만 사용할 것을 권한다.
    Example
    Reference Ducumment
    << trace의 기능을 이용하여 trace를 할수 있는 component들 >>
    * Network listener
    * Net8 components on the client and server
    * Connection Manager
    * Oracle Names Server
    * Oracle Names Control Utility
    * TNSPING utility
    2. 어떤 parameter들을 설정하면 trace 기능을 이용할 수 있는가 ?
    tracing을 하기 위해서는 특정 trace parameter들을 설정함으로써 가능하며
    아래에 주어진 방법들과 또는 utility들중 하나를 선택하여 설정함으로써
    사용할 수 있다.
    * Component Configuration Files
    * Component Control Utilities
    * Oracle Trace
    component의 configuration 파일을 이용하여 traceing parameter를 설정하려면
    1) component의 configuration 파일에 다음의 traceing parameter를 설정한다.
    - SQLNET.ORA for client or server, LISTENER.ORA for listener:
    TRACE_LEVEL_<CLIENT/LISTENER/SERVER>=(0/4/10/16)
    TRACE_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    LOG_DIRECTORY_<CLIENT/LISTENER/SERVER>=<directory name>
    2) 만일 component들이 수행중인 동안 configuration 파일의 수정이 있었다면
    변경된 parameter들을 사용하기 위해 component들을 다시 시작하여야 한다.
    component control utility들을 이용하여 trace parameter들을 설정하려면
    1) listener의 경우, Listener Control Utility(lsnrctl)에서 TRACE 명령어를
    이용하여 listener가 수행중인 동안에도 trace level을 설정할 수 있다.
    EX)
    RC80:/mnt3/rctest80> lsnrctl
    LSNRCTL for SVR4: Version 8.0.4.0.0 - Production on 01-SEP-98 15:16:52
    (c) Copyright 1997 Oracle Corporation. All rights reserved.
    Welcome to LSNRCTL, type "help" for information.
    LSNRCTL> trace admin
    Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
    Opened trace file: /mnt4/coe/app/oracle/product/8.0.4/network/trace/
    lsnr_coe.trc
    The command completed successfully
    LSNRCTL> trace off
    Connecting to (ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
    The command completed successfully
    LSNRCTL> exit
    RC80:/mnt3/rctest80>
    2) Oracle Names의 경우, Names Control Utility(namesctl)에서 TRACE_LEVEL
    명령어를 이용하여 Oracle Names가 수행중인 동안에도 trace level을
    설정할 수 있다.
    주의 : Connection Manager의 경우, trace level은 configuration 파일인
    CMAN.ORA 에서만 설정할 수 있다.
    Oracle Enterprose manager(이하 OEM)에 있는 Oracle Trace는 trace parameter
    들을 설정하고 GUI를 통해 trace data의 형태를 볼수 있도록 하는 tracing tool
    이다.
    3. Trace된 data를 해석할 수 있는 다른 utility들이 있다면 ?
    Trace Assistant를 사용하면 사용자의 *.trc 파일 (SQL*Net v2의 형식에 의해
    생성된) 또는 *.txt (Orace Trace 과 TRCFMT에 의해 생성된 출력물)을 통해
    trac된 정보를 해석할 수 있다.
    이 유틸리티 네트워크의 문제들로 인해 발생하는 문제점들을 진단하고
    해결하는 데 보다 많은 정보를 제공하여 사용자의 이해를 돕는다.
    * the source and destination of trace files
    * the flow of packets between network nodes
    * which component of Net8 is failing
    * pertinent error codes
    다음에 주어진 명령어를 수행하므로써 Trace Assistant 실행할 수 있다.
    trcasst [options] <filename>
    Trace Assistant Text Formatting Options
    -o Displays connectivity and Two Task Common (TTC) information.
    After the -o the following options may be used:
    c (for summary connectivity information)
    d (for detailed connectivity information)
    u (for summary TTC information)
    t (for detailed TTC information)
    q (displays SQL commands enhancing summary TTC
    information)
    -p Oracle Internal Use Only
    -s Displays statistical information
    -e Enables display of error information After the -e, zero
    or one error decoding level may follow:
    0 or nothing (translates the NS error numbers dumped
    from the nserror function plus lists all
    other errors)
    1 (displays only the NS error translation from
    the nserror function)
    2 (displays error numbers without translation)
    만일 option들이 제공되지 않는다면 기본적으로 -odt -e -s가 지정되어 자세한
    connectivity, Two-Task Common, 에러 level 0 그리고 통계정보들이 tracing
    된다.
    4. SQL*Net v2 tracing과 어떻게 다른가 ?
    Net8 tracing에서는 이전 버전인 SQL*NET V2에서 제공 되는 모든 option을
    포함하고 있고 Oracle Trace의 기능이 추가되었다.
    이것은 Oracle Trace Repository를 OEM 콘솔을 통하여 사용자의 trace 정보를
    관리할 수 있도록 허용한다.
    5. *.cdf와 *.dat은 어떤 파일 인가 ?
    *.cdf 와 *.dat 파일들은 Oracle Trace에 의해 생성되는 파일들로서 이 파일들을
    읽기 위해서는 반드시 trcfmt utility를 이용해야만 한다.
    trcfmt는 binary (*.dat와 *.cdf의 확장자) 파일내에 있는 data를 일반text
    (.txt의 확장자)로 정보를 추출한다. 이 tool을 사용하기 위해서는 다음의
    명령어를 이용하면 된다.
    $ trcfmt collection.cdf
    주의 : .cdf와 .dat파일이 존재하는 디렉토리가 아닌 곳에서 이 tool을 이용
    한다면 path가 포함되야 한다. 만일 하나의 .cdf 와 .dat 파일들내에
    여러 프로세스들의 traceing정보가 수집된다면 그것들은 process_id.txt
    의 이름과 함께 파일이 추출될 것이다.
    6. trac관련 configuration은 어떤 것이 있으며 설정할 수 있는 parameter는
    무엇이 있는가 ?
    ==========================================================================
    || SQLNET.ORA Parameters ||
    ==========================================================================
    DAEMON.TRACE_DIRECTORY
    Purpose: Controls the destination directory of the Oracle
    Enterprise Manager daemon trace file
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_DIRECTORY=/oracle/traces
    DAEMON.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level for
    the Oracle Enterprise Manager daemon.
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_LEVEL=10
    DAEMON.TRACE_MASK
    Purpose: Specifies that only the Oracle Enterprise Manager daemon
    trace entries are logged into the trace file.
    Default Value: $ORACLE_HOME/network/trace
    Description
    Available Oracle Enterprise Manager Installation Guide
    Example: DAEMON.TRACE_MASK=(106)
    LOG_DIRECTORY_CLIENT
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_CLIENT=/oracle/network/trace
    LOG_DIRECTORY_SERVER
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Valid in File: SQLNET.ORA
    Example: LOG_DIRECTORY_SERVER=/oracle/network/trace
    LOG_FILE_CLIENT
    Purpose: Controls the log output filename for an Oracle client.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_CLIENT=client
    LOG_FILE_SERVER
    Purpose: Controls the log output filename for an Oracle server.
    Default Value: SQLNET.LOG
    Example: LOG_FILE_SERVER=svr
    NAMESCTL.TRACE_LEVEL
    Purpose: Indicates the level at which the NAMESCTL program should
    be traced.
    Default Value: OFF
    Values: OFF, USER, or ADMIN
    Example: NAMESCTL.TRACE_LEVEL=ADMIN
    NAMESCTL.TRACE_FILE
    Purpose: Indicates the file in which the NAMESCTL trace output is
    placed.
    Default Value: namesctl_PID.cdf and namesctl_PID.dat
    Example: NAMESCTL.TRACE_FILE=NMSCTL
    NAMESCTL.TRACE_DIRECTORY
    Purpose: Indicates the directory where trace output from the NAMESCTL
    utility is placed.
    Default
    Value: $ORACLE_HOME/network/trace
    Example: NAMESCTL.TRACE_DIRECTORY=/ORACLE/TRACE
    NAMESCTL.TRACE_UNIQUE
    Indicates whether a process identifier is appended to the
    Purpose: name of each trace file generated, so that several can
    coexist.
    Default
    Value: OFF
    Values: OFF or ON
    Example: NAMESCTL.TRACE_UNIQUE = ON
    TNSPING.TRACE_DIRECTORY
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TNSPING.TRACE_DIRECTORY=/oracle/traces
    TNSPING.TRACE_LEVEL
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TNSPING.TRACE_LEVEL=10
    TRACE_DIRECTORY_CLIENT
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_CLIENT=/oracle/traces
    TRACE_DIRECTORY_SERVER
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_SERVER=/oracle/traces
    TRACE_FILE_CLIENT
    Purpose: Controls the name of the client trace file
    Default Value: SQLNET.CDF and SQLNET.DAT
    Example: TRACE_FILE_CLIENT=cli
    TRACE_FILE_SERVER
    Purpose: Controls the name of the server trace file
    Default Value: SVR_PID.CDF and SVR_PID.DAT
    Example: TRACE_FILE_SERVER=svr
    TRACE_LEVEL_CLIENT
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_CLIENT=10
    TRACE_LEVEL_SERVER
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 or SUPPORT - WorldWide Customer Support trace
    information
    Example: TRACE_LEVEL_SERVER=10
    TRACE_UNIQUE_CLIENT
    Used to make each client trace file have a unique name to
    Purpose: prevent each trace file from being overwritten with the next
    occurrence of the client. The PID is attached to the end of
    the filename.
    Default
    Value: OFF
    Example: TRACE_UNIQUE_CLIENT=ON
    USE_CMAN
    If the session is in an Enhanced Discovery Network with a
    Purpose: Names Server, this parameter forces all sessions to go
    through a Connection Manager to get to the server.
    Default
    Value: FALSE
    Values: TRUE or FALSE
    Example: USE_CMAN=TRUE
    ==========================================================================
    || LISTENER.ORA Parameters ||
    ==========================================================================
    LOG_DIRECTORY_listener_name
    Purpose: Controls the directory for where the log file is written
    Default Value: Current directory where executable is started from.
    Example: LOG_DIRECTORY_LISTENER=/oracle/traces
    LOG_FILE_listener_name
    Purpose: Specifies the filename where the log information is
    written
    Default Value: listener_name.log
    Example: LOG_FILE_LISTENER=lsnr
    TRACE_DIRECTORY_listener_name
    Purpose: Control the destination directory of the trace file
    Default Value: $ORACLE_HOME/network/trace
    Example: TRACE_DIRECTORY_LISTENER=/oracle/traces
    TRACE_FILE_listener_name
    Purpose: Controls the name of the listener trace file
    Default Value: LISTENER_NAME.CDF and LISTENER_NAME.DAT
    Example: TRACE_FILE_LISTENER=lsnr
    TRACE_LEVEL_listener_name
    Purpose: Turns tracing on/off to a certain specified level
    Default Value: 0 or OFF
    * 0 or OFF - No trace output
    * 4 or USER - User trace information
    Available Values
    * 10 or ADMIN - Administration trace information
    * 16 - WorldWide Customer Support trace information
    Example: TRACE_LEVEL_LISTENER=10
    ==========================================================================
    || NAMES.ORA Parameters ||
    ==========================================================================
    NAMES.TRACE_DIRECTORY
    Purpose: Indicates the name of the directory to which trace files
    from a Names Server trace session are written.
    Default
    Value: platform specific
    Example: names.trace_directory = complete_directory_name
    NAMES.TRACE_FILE
    Purpose: Indicates the name of the output file from a Names Server
    trace session. The filename extension is always.trc
    Default
    Value: names
    Example: names.trace_file = filename
    NAMES.TRACE_LEVEL
    Purpose: Indicates the level at which the Names Server is to be
    traced.
    Default Value: OFF
    Example: names.trace_level = OFF
    NAMES.TRACE_UNIQUE
    indicates whether each trace file has a unique name, allowing
    Purpose: multiple trace files to coexist. If the value is set to ON, a
    process identifier is appended to the name of each trace file
    generated.
    Default
    Value: OFF
    Example: names.trace_unique = ON
    names.trace_file = names_05.trc
    ==========================================================================
    CMAN.ORA Parameters
    ==========================================================================
    TRACING
    Default
    Value: NO
    Example: TRACING = NO
    References
    7. listener.log 파일에 loggin정보를 남기지 않게 하는 방법이 있나요 ?
    고객이 개발하여 사용중인 application에서 NET8을 이용하여 접속하거나 접속을
    종료하는 경우 listener.log에 이와 관련된 정보가 남으며, 수 많은 사용자가
    접속을 하게 되므로서 급속하게 listener.log 파일이 커져 $ORACLE_HOME이 있는
    file system이 꽉 차서 데이터베이스가 hang이 되는 결과를 초래하는 경우가 있다.
    고객들은 listener.log에 write할수 있는 메세지의 양에 제한을 두기를 원하는
    경우가 있으나 이러한 기능은 제공되지 않는다. 하지만 listener의 logging은
    ON 또는 OFF는 설정을 통해서 가능하다.
    Net8에서는 listener.ora에 "LOGGING_(the listener name)=off"를 설정하게
    되면 listener의 logging을 멈출 수 있다.
    물론 설정후 listener stop후 재기동을 하셔야 변경된 paramerter에 의해
    이 기능이 enable됩니다.
    참고 : SQL*NET 2.3.x 에서도 이 parameter가 유효한가요 ?
    물론 사용이 가능합니다. NET8에서 사용하는 것과 동일하게 parameter를
    listener.ora에 설정함으로서 가능합니다.
    EX)
    LOGGING_LISTENER=OFF
    이 parameter는 listener의 전체 logging을 disable하는 parameter로 일부만
    여과하여 logging할 수 있는 기능은 아니다.
    이 parameter는 NET8에 알려진 parameter로 SQL*NET 2.3.x manuals에 나와
    있지는 않지만 정상적으로 사용할 수 있다.

Maybe you are looking for