Enable logging level

hi all,
in our company, we are maintaing users for OBIEE in the external table and admin tool.
i am able set logging level for the users in the admin tool. but could not set logging level for users maintained in the external table.
please let me now how to enable loggin level for users maintained in the external table.
thanks

You can set it in your authorisation init_block by setting the LOGLEVEL variable.
regards
John
http://obiee101.blogspot.com/

Similar Messages

  • How to enable "top level navigation " in portal

    Hi all,
    I am unable to see the "top level Navigation" once I logged on to portal
    Previously I was able to see that
    I performed the following steps thats the reason why I am unable to see "top level navigation"
    1 Logged on to portal
    2 Content administration
    3 Expanded Poratl Content
    4 Expanded Content Provided by SAP
    5 Expanded End User Content
    6 Expanded Standard Poratl Users
    7 Selected "Default Frame work Page"
    8 In that selected Top Level navigation Iview and the iveiw properties I changed the property "Number of Display Levels " to "0" and choose save
    As I have set "Number of Display Levels" to "0" I am unable to see "top level Navigation" Now,I want to change it to 2 for that I need to see the Content Administration role in the "Top Level navigation" Can anyone help me out how to enable "Top level Navigation"
    Thanks in advance

    undo the changes what you have done.
    after you logon to the portal try the url below...this should take you to content admin directly from there modify the framework page and reset the property of TLN
    http://yourserver:port/irj/servlet/prt/portal/prtroot/com.sap.portal.pagebuilder.IviewModeProxy?iview_id=pcd%3Aportal_content%2Fadministrator%2Fsuper_admin%2Fsuper_admin_role%2Fcom.sap.portal.content_administration%2Fcom.sap.portal.content_admin_ws%2Fcom.sap.portal.portal_content&iview_mode=default
    Thanks
    GLM

  • How to Enable logging of the ASA 5525?

    I need help to enable logging of the ASA 5525 for all new rules created today from the firewall module, rules changed, deleted desabilidas and disabled rules.
    Not found in the historic level of the ID on new firewall rules.
    0 or emergencies—System is unusable.
    1 or alerts—Immediate action needed.
    2 or critical—Critical conditions.
    3 or errors—Error conditions.
    4 or warnings—Warning conditions.
    5 or notifications—Normal but significant conditions.
    6 or informational—Informational messages.
    7 or debugging—Debugging messages.
    Thank you.

    You cannot log only those changes but you can log *all* changes.
    The messages 111008 and 111010 are the ones to look for (as described in this post).

  • Could you tell me what's the meaning of the logfile-path and log-level?

    we are running an productive xml database. but it is not stable now. Sometime it would report resource conflict error while you access xmldb via http protocol. I read the database logs and listener logs, but no abnormal message could be found. So, I want to find more information from the xmldb logs. While I run select DBMS_XDB.cfg_get().getclobval() from dual, I found that there are several logfile-path and log-level tags and I guess that these would be xmldb logs. Does anyone know what's the meaning of these tags?

    I wondered about that one often too. I didn't have a chance yet to investigate (but maybe Mark will elaborate a little here), my guess is that it / or will be a possibility to enable tracing regarding the protocols or servlets.
    Though It look like if you enable it it will trace to the XML file defined in the xdbconfig.xml. I also guess that (because there is also a XSD counterpart) that one could create an resource that streams the errors into a XDB ftp or http or ... xmltype table based on these settings.
    This would be great because it would mature the protocol server regarding functionality. You could enable the tracing and see what happens. Until now the documentation doesn't give much extra insight...
    <!-- FTP specific -->
    <element name="ftpconfig">
    <complexType><sequence>
    <element name="ftp-port" type="unsignedShort" default="2100"/>
    <element name="ftp-listener" type="string"/>
    <element name="ftp-protocol" type="string"/>
    <element name="logfile-path" type="string" default="/sys/log/ftplog.xml"/>
    <element name="log-level" type="unsignedInt" default="0"/>
    <element name="session-timeout" type="unsignedInt" default="6000"/>
    <element name="buffer-size" default="8192">
    <simpleType>
    <restriction base="unsignedInt">
    <minInclusive value="1024"/> <!-- 1KB -->
    <maxInclusive value="1048496"/> <!-- 1MB -->
    </restriction>
    </simpleType>
    </element>
    <element name="ftp-welcome-message" type="string" minOccurs="0"
    maxOccurs="1"/>
    </sequence></complexType>
    </element>
    <!-- HTTP specific -->
    <element name="httpconfig">
    <complexType><sequence>
    <element name="http-port" type="unsignedShort" default="8080"/>
    <element name="http-listener" type="string"/>
    <element name="http-protocol" type="string"/>
    <element name="max-http-headers" type="unsignedInt" default="64"/>
    <element name="max-header-size" type="unsignedInt" default="4096"/>
    <element name="max-request-body" type="unsignedInt" default="2000000000"
    minOccurs="1"/>
    <element name="session-timeout" type="unsignedInt" default="6000"/>
    <element name="server-name" type="string"/>
    <element name="logfile-path" type="string"
    default="/sys/log/httplog.xml"/>
    <element name="log-level" type="unsignedInt" default="0"/>
    <element name="servlet-realm" type="string" minOccurs="0"/>
    ...etc...

  • XMLDB log-level configuration

    I've been searching for a document that will advise what the different log-level settings are that can be put into the xdbconfig.xml but I can't seem to find anything on this. The default level is set to 0 on install. That is what we current have it as. We are being required to make this a log-level of 1 but I don't know the implications of doing this.
    Does anyone know where I can find more information regarding this? We have an Oracle 11.1.0.7 installation on AIX 7.1 -- any help would be appreciated.

    Apparently the IRS does know, once again, more then I do ;-)
    Seriously; The status of 2007 does not have changed for this feature.
    The following is a feature that does work: http://www.liberidu.com/blog/2010/01/17/ora-31098-internal-event-to-turn-on-xdb-tracing
    Also you can enable the listener logging/tracing which will also mention login attempts (and TCP/IP#, FQDN info btw).
    The XFiles demo XMLDB app also shows a method on how to program this feature via XDB events and stuff...
    The needed info, probably, can also retrieved by implementing Database Vault or the Database Firewall software (and yes, security comes at a cost).
    http://www.oracle.com/technetwork/products/database-firewall/overview/index.html
    Edited by: Marco Gralike on Sep 20, 2012 3:07 AM

  • Enabling item level security

    Hi,
    We are using portal version 3.0.9. We are trying to implement security at the item level and have super-user rights. According to <http://portalstudio.oracle.com/help/sblgrapi.htm>, if you scroll all the way to the bottom it says that "You cannot enable item level security for items in the Portlet Repository content area." I am assuming that this Portlet Repository content area is referring to the Administer->Display Portlet Repository ->Seeded Providers -> Portal Content Area -> Content Areas
    The items that we want to secure are currently in the folder called "other providers" but I can also access the items from within the portal repository content areas.
    So far I have been specifying access to the page, the category, the folder, and the item, and when I log in as a view only user I still can see things that I shouldn't. Perhaps, it is because it is somehow still in the repository?
    I think that I am missing a step somewhere. I have cleared inherit privileges and enable item level security wherever I could find that option while editing. Has anyone successfully added security to even a folder?
    Thanks in advance.
    Best Regards,
    Lindsay

    Lindsay,
    I'm not sure if this is what you are looking for, but you can secure access to portlets that are shown in the portlet repository
    through the Access tab that is available when you "Edit" the portlet entry in the Edit Folder view of the Portlet repository.
    [ol]
    [li]Go to the portlet repository
    [li]Navigate to the appropriate folder
    [li]Edit the folder
    [li]Click on the Edit link beside the portlet of interest
    [li]Click on the Access tab
    [li]Turn on access control and specify privileges on the portlet.
    [ol]
    See if this is what you are looking for, or let me know if I'm off base.

  • When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode

    Question :
    When creating a tablespace why should we enable LOGGING when a database is already on ARCHIVE LOG mode ?
    Example:
    Create Tablespace
    CREATE SMALLFILE TABLESPACE "TEST_DATA"
    LOGGING
    DATAFILE '+DG_TEST_DATA_01(DATAFILE)' SIZE 10G
    AUTOEXTEND ON NEXT  500K MAXSIZE 31000M
    EXTENT MANAGEMENT LOCAL
    SEGMENT SPACE MANAGEMENT AUTO;
    LOGGING: Generate redo logs for creation of tables, indexes and  partitions, and for subsequent inserts. Recoverable
    Are they not logged and not recoverable if we do not enable LOGGING? What is that ARCHIVELOG mode does?

    What is that ARCHIVELOG Mode Does?
    Whenever your database is in archive log mode , Oracle will backup the redo log files in the form of Archives so that we can recover the database to the consistent state in case of any failure.
    Archive logging is essential for production databases where the loss of a transaction might be fatal.
    Why Logging?
    Logging is safest method to ensure that all the changes made at the tablespace will be captured and available for recovery in the redo logs.
    It is just the level at which we defines:
    Force Logging at DB level
    Logging at Tablespace Level
    Logging at schema Level
    Before the existence of FORCE LOGGING, Oracle provided logging and nologging options. These two options have higher precedence at the schema object level than the tablespace level; therefore, it was possible to override the logging settings at the tablespace level with nologging setting at schema object level.

  • Unable to enable logging for AD connector

    I cant enable log for my AD connector because when i set environment variable
    WLS_REDIRECT_LOG = F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\oim_server1-diagnostic-1.log
    and restart server its starts logging everything in the oim_server1-diagnostic-1.log... even it ask the username and password in this log file....
    Any Solution will be appreciated

    The configuration file for OJDL is logging.xml, which is located at the following path:
    DOMAIN_HOME/config/fmwconfig/servers/OIM_SERVER/logging.xml
    Here, DOMAIN_HOME and OIM_SERVER are the domain name and server name
    specified during the installation of Oracle Identity Manager.
    e.g. /home/ofmuser/fusion/Middleware/user_projects/domains/oimdomain/config/fmwconfig/servers/oim_server1
    <?xml version="1.0" encoding="UTF-8"?>
    <logging_configuration>
    <log_handlers>
    <log_handler name='adcs-handler' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
    <property name='logreader:' value='off'/>
    <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/LOGFILE_NAME.log'/>
    <property name='format' value='ODL-Text'/>
    <property name='useThreadName' value='true'/>
    <property name='locale' value='en'/>
    <property name='maxFileSize' value='5242880'/>
    <property name='maxLogSize' value='52428800'/>
    <property name='encoding' value='UTF-8'/>
    </log_handler>
    <logger name="OIMCP.ADCS" level="TRACE:32" useParentHandlers="false">
    <handler name="adcs-handler"/>
    <handler name="console-handler"/>
    </logger>
    replace LOG_LEVEL as TRACE:32
    replace LOGFILE_NAME with proper name
    first part put in log_handler
    and the second part put into logger section
    regards,
    nayan
    Edited by: Nishith Nayan on Jan 17, 2012 11:00 PM

  • Change opmn log level

    how to change opmn log level in OAS 10.1.3.3. I want to set it to debug level.
    Thanks
    AB

    Thanks, I looked at the following section but still not sure what exactly to change in opmn.xml
    2.2 There used to be a level attribute in the <log-file> tag that I don’t find anymore. How do I define log levels?
    In 10.1.3.1.0, logging is configured by component codes rather than level codes. The logging messages contain the literal value based on logging levels rather than an integer value; for example: none, fatal, error, warn, notify, debug1, debug2, debug3, and debug4.
    All OPMN log messages of non-debug type (none, fatal, error, warn and notify) for the ONS and PM components go in opmn.log file. If debugging is enabled, then all OPMN debug log messages (of type debug1, debug2, debug3 and debug4) are written into opmn.dbg file.
    You can configure the following component codes for logged events for both log and debug:
    • internal: a log for the common internal information for OPMN
    • ons: a log for the ONS component information for OPMN
    • pm: a log for the PM component information for OPMN
    Both the ons and pm components consist of subcomponents that can also be configured. Refer to the Oracle Process Manager and Notification Server Administrator’s Guide 10g Release 3 (10.1.3.1.0) for the list of ons and pm subcomponents.
    I looked at http://download-west.oracle.com/docs/cd/B25221_04/core.1013/b15976/common.htm#g1044967
    and there is a section
    <debug>
    Required: false
    Default: see attributes
    Parents: <opmn>
    Attributes: path, comp, rotation-size, rotation-hour
    Can you tell me an example how i can set it?

  • Cflog & fix server log level

    Hello,
    I can't find information about how to set the log level on
    cold fusion server config.
    cflog tag enable a type of log, and I don't want to see debug
    information on live servers.
    Bonus question: do we have a way to put code execution for
    debug only, such as "<cfif_debug_mode><cfoutput>#my
    super debuginfo#</cfoutput></cfif_debug_mode>"
    Thanks,
    Yoann.

    Thanks, I've found the link between the admin option "Enable
    Request Debugging Output" and the "IsDebugMode()", very usefull.
    But still nothing related to "type of log" and a
    configuration parameter to set the severity level of log.
    Type of log are defined as:
    * Information
    * Warning
    * Error
    * Fatal
    I would like to set on prod server a log level to "Error"
    only...
    It seems that an alternative way would be to use "cftrace"
    for debug info, that can be disable by admin parameter. (but as far
    as the application already exist, it means re-writing some
    APIs)

  • Enabling logging for ACF2 OIM 11g

    Hi Experts,
    I want to enable logging for ACF2 connector, I want to implement the logging in OJDL as per provided by 11g.
    But in deployment guide for ACF2 i see under section of enabling logging has:
    log4j.logger.COM.IDENTITYFORGE.ORACLE.INTEGRATION.IDFACF2USEROPERATIONS=INFO
    The connector is the latest one 9.0.4.18 version.
    seems they have still leveraged Log4j.. Does is work in OIM 11g, is there a way to implement OJDL. Please help!!

    Normally we configure OJDL it will be fine for OIM
    http://idmoim.blogspot.in/2011/07/enabling-logging-in-oim-11g.html
    what you are pointing is about Ldap Gateway. and ldap gateway still having log4j. go through the connector doc you will get all the required steps
    yes for capturing ldap gateway operations log you have to enable log4j.it is fine with 11g as well
    below from connector doc:(2.9 Installing and Configuring the LDAP Gateway)
    7. To enable logging for the LDAP Gateway:
    a. Copy the log4j JAR file from the application server directory in which it is
    placed to the LDAP_INSTALL_DIR/lib directory.
    b. Extract the log4j.properties file from the
    LDAP_INSTALL_DIR/dist/idfserver.jar file.
    c. Enter a log level as the value of the log4j.rootLogger variable. For example:
    log4j.rootLogger=ERROR, A1
    d. Save and close the file.
    When you use the connector, the following log files are generated in the
    LDAP_INSTALL_DIR/logs directory:
    ■ idfserver.log.0: This is the main log file.
    ■ acf2-agent-recon.log: This is the real-time, incremental reconciliation log file
    that stores Oracle Identity Manager reconciliation messages.

  • Enabling logging in OIM11gR2

    Hi Experts,
    I am creating a Custom Adaptor using Java task, I want to track my code using some logging or want to debug it to checkits execution. Is there a way to enable its logging/code snippet or any inbuilt way inOIM11gR2.
    Thanks

    why are you trying for log4j. You have OJDL in 11g and this is working fine.
    find the below steps
    Add the following line into your java code.
    Import Statement
    import com.thortech.util.logging.Logger;
    private Logger logger=Logger.getLogger("Logger-Name");
    Configuration Of Logging
    Go to the $DOMAIN_HOME/config/fmwconfig/servers/oim_server1 directory and edit the logging.xml file.
    Configure The Log Handler
    <log_handler name='logger Handel Name' level='FINEST' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
    <property name='logreader:' value='off'/>
    <property name='path' value='Log File Location'/>
    <property name='format' value='ODL-Text'/>
    <property name='useThreadName' value='true'/>
    <property name='locale' value='en'/>
    <property name='maxFileSize' value='5242880'/>
    <property name='maxLogSize' value='52428800'/>
    <property name='encoding' value='UTF-8'/>
    Include The Logger Handler Logger Configuration
    <logger name="Logger-Name" level="Log Level" useParentHandlers="false">
    <handler name="logger-Handel-Name"/>
    <handler name="console-handler"/>
    </logger>
    Oracle Identity Manager 11G Log Levels
    Log Level ODL Message Type:Level
    SEVERE.intValue()+100 INCIDENT_ERROR:1
    SEVERE ERROR:1
    WARNING WARNING:1
    INFO NOTIFICATION:1
    CONFIG NOTIFICATION:16
    FINE TRACE:1
    FINER TRACE:16
    FINEST TRACE:32
    The FINEST log level will give the more debug info. If you want to debug your schedule task or event handlers, please use FINEST Log level.

  • Enabling Logging on an ASR from a source port

    I have a Cisco ASR 1001.  I am trying to send traffic from g0 to a switch that picks up all my logging traffic.
    Below is my config.  What am I missing.  I am trying to send traffic to device 10.10.23.17. I want to make sure that ll traffic get to 10.10.23.17.
    Thanks in advance!
    logging trap debugging
    logging facility local1
    logging host 10.10.23.17
    ip route vrf Mgmt-intf 0.0.0.0 0.0.0.0 10.10.88.1

    Syslog logging: enabled (0 messages dropped, 11 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
    No Active Message Discriminator.
    No Inactive Message Discriminator.
        Console logging: disabled
        Monitor logging: disabled
        Buffer logging:  disabled, xml disabled,
                        filtering disabled
        Exception Logging: size (4096 bytes)
        Count and timestamp logging messages: disabled
        Persistent logging: disabled
    No active filter modules.
        Trap logging: level debugging, 553 message lines logged
            Logging to 10.10.23.17  (udp port 514, audit disabled,
                  link up),
                  121 message lines logged,
                  0 message lines rate-limited,
                  0 message lines dropped-by-MD,
                  xml disabled, sequence number disabled
                  filtering disabled
            Logging to 10.10.89.74  (udp port 514, audit disabled,
                  link up),
                  2 message lines logged,
                  0 message lines rate-limited,
                  0 message lines dropped-by-MD,
                  xml disabled, sequence number disabled
                  filtering disabled
            Logging Source-Interface:       VRF Name:
            GigabitEthernet0                Mgmt-intf

  • How do I set the logging level with the plug-in 1.4

    I am writing an applet that will be hosted in the plug-in version 1.4. I'd like to set up some logging statements using the java.util.logging API. I have successfully got it to print out log messages, but it is not printing anything below level INFO. How can I set it up to print out log statements at the FINEST level?

    If you are using the default logger for logging from the applet, the default log level from the logging.properties file in your JRE lib directory is the place. There is an entry
        .level= INFO In this file. You can modify this entry.
    This is a a roundabout way of achieving it. since we are modifying the default log level here, it will be used by other java applications as well. I am looking for a better solution.

  • Error while Changing log level in Agentry 6.0.44.1

    Hi ,
    I am trying to change the log level from the Agentry Administration client, but i am getting the below error message.
    And it is showing any option to change the log levels for users. How can I change log level for users also.
    How can I resolve this error.
    Regards,
    Shyam

    Shyam,
    This is fixed or planned fixed in 6.0.46 Agentry Server (supposed to be available anytime soon in the Service Marketplace - it was submitted already to the SMP team). The fix was in SMP 2.3 and SMP 3.0 but it was ported back to the Agentry 6.0.X release. If you have no access to the Agentry 6.0.X patches this means that your SAP License is preventing you from downloading it. You may need to contact the SAP CIC (customer interaction center) group.
    Or you can do the manual setup for a workaround for now.
    SAP KBA article: 2048202 - AgentryGUI does not allow to change log settings - Not all setttings were successfully changed.
    Regards,
    Mark Pe
    SAP Senior Support Engineer (Mobility)

Maybe you are looking for