Specific Level for Log

Hi !
Is this possible to define some new and specific log level for our own application, for example a TRAP level ?
If yes:
How is inserted this new Level in the existing ones ? if I want this TRAP level to be located between INFO and CONFIG, possible ?
Thanks
Regards
Ludovic Maillet

I asked this question because I saw this in the Javadoc (1.4):
protected Level(String name,
int value)Create a named Level with a given integer value.
Note that this constructor is "protected" to allow subclassing. In general clients of logging should use one of the constant Level objects such as SEVERE or FINEST. However, if clients need to add new logging levels, they may subclass Level and define new constants.
??

Similar Messages

Setting privilege level for logging into ASA through ACS

Hi!,
In my environment i implemented AAA for logging into switches, routers, asa etc through ACS which is being configured TACACS+.
I have set different privilege levels like readonly, readwrite etc into ACS. There are working fine when i try to login into switch or router.
But in ASA i am unable to restrict the privilege levels of different users.
Can someone plz guide me with ASA & ACS setting to solve this issue!!!!!

Hi!!
I tried this option. It is working fine with routers & switches. But for ASA privilege access it is not functioning.
I created 3 profiles in "Shared Profiles" & added 1 of them in Group setting & added users to this group with mentioning group authentication. This way i am able to control access to the switches & routers with proper privilege. But the same way when i tried to impolement ASA it's not happening.
Can u plz check it out...

Java.util.logging - Problem with setting different Levels for each Handler

Hello all,
I am having issues setting up the java.util.logging system to use multiple handlers.
I will paste the relevant code below, but basically I have 3 Handlers. One is a custom handler that opens a JOptionPane dialog with the specified error, the others are ConsoleHandler and FileHandler. I want Console and File to display ALL levels, and I want the custom handler to only display SEVERE levels.
As it is now, all log levels are being displayed in the JOptionPane, and the Console is displaying duplicates.
Here is the code that sets up the logger:
logger = Logger.getLogger("lib.srr.applet");
// I have tried both with and without the following statement
logger.setLevel(Level.ALL);
// Log to file for all levels FINER and up
FileHandler fh = new FileHandler("mylog.log");
fh.setFormatter(new SimpleFormatter());
fh.setLevel(Level.FINER);
// Log to console for all levels FINER and up
ConsoleHandler ch = new ConsoleHandler();
ch.setLevel(Level.FINER);
// Log SEVERE levels to the User, through a JOptionPane message dialog
SRRUserAlertHandler uah = new SRRUserAlertHandler();
uah.setLevel(Level.SEVERE);
uah.setFormatter(new SRRUserAlertFormatter());
// Add handlers
logger.addHandler(fh);
logger.addHandler(ch);
logger.addHandler(uah);
logger.info(fh.getLevel().toString() + " -- " + ch.getLevel().toString() + " -- " + uah.getLevel().toString());
logger.info("Logger Initialized.");Both of those logger.info() calls displays to the SRRUserAlertHandler, despite the level being set to SEVERE.
The getLevel calls displays the proper levels: "FINER -- FINER -- SEVERE"
When I start up the applet, I get the following in the console:
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.Notice they all display twice. Each of those are also being displayed to the user through the JOptionPane dialogs.
Any ideas how I can properly set this up to send ONLY SEVERE to the user, and FINER and up to the File/Console?
Thanks!
Edit:
Just in case, here is the code for my SRRUserAlertHandler:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          JOptionPane.showMessageDialog(null, arg0.getMessage());
}Edited by: compbry15 on Apr 28, 2009 9:44 AM

For now I have fixed the issue of setLevel not working by making a Filter class:
public class SRRUserAlertFilter implements Filter {
     public boolean isLoggable(LogRecord arg0) {
          if (arg0.getLevel().intValue() >= Level.WARNING.intValue()) {
               System.err.println(arg0.getLevel().intValue() + " -- " + Level.WARNING.intValue());
               return true;
          return false;
}My new SRRUserAlertHandler goes like this now:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          Filter theFilter = this.getFilter();
          if (theFilter.isLoggable(arg0))
               JOptionPane.showMessageDialog(null, arg0.getMessage());
}This is ugly as sin .. but I cannot be required to change an external config file when this is going in an applet.
After much searching around, this logging api is quite annoying at times. I have seen numerous other people run into problems with it not logging specific levels, or logging too many levels, etc. A developer should be able to complete configure the system without having to modify external config files.
Does anyone else have another solution?

How to make Delivery block at Sales Order Header level for specific materia

Hi,
My client want to create a delivery block EDI order at the Order Header level for specific materials
How can we achieve this.

Dear Varada rajan
Go to material master, select "Sales: sales org.1" view and assign "01" against the field "DChain-spec. status" and save. By assigning, for a particular sales area, you can block that material.
Now go to OVSU select 01 and assign "B" against the field "Block delivery".
Now create a sale order and post the outcome.
thanks
G. Lakshmipathi

How to set more detail log level for http

Hi,
With Java Enterprise System 2003 I want to see when a user login to the Messenger Express in the http log. How could I set a log level so I can see this?
I do not know the the default log level for http and I would like to set a log level that show me more information
could this be the command?
configutil -o logfile.http.loglevel -v level Information

configutil -o logfile.http.loglevel -v Information
would be the correct command to set the log level to "information".
Other valid levels include, "debug", "notice" (this is the default), "warning".
You have t restart the webmail daemon to make this take effect.
stop-msg http; start-msg http

How to increase log level for SUNW.oracle_listener resource type

I understand that i can increase logging level for a resource with "clrs set -p "Debug_level=$LEVEL", but the SUNW.oracle_listener resource type doesn't seem to have this property. Is there some other way of increasing log data to debug an issue with a listener resource? I ask because we have a strange situation where our database listener is being restarted every once in a while. With the log data I have, it appears that the listener is being stopped or dies, and then the monitor restarts it when it detects the fault, however our DBA's believe that it is the cluster that is actually the one cycling it because the monitor fails or is unable to connect because it is too busy to respond in time or something along those lines.
Maybe I am incorrect and it is the cluster, but I'd expect to see something before a "Attempting to restart listener" log entry, something along the lines of the monitor failing or a "no response in given time" before the resource says it is restarting.
Here are the logs from when this first happens, if anyone can advise, I would really appreciate it.
Sep 28 14:17:48 SC[SUNWscor.oracle_listener.monitor]:oracle:oraclels: Attempting to restart listener oracle.
Sep 28 14:17:50 SC[SUNWscor.oracle_listener.monitor_stop]:oracle:oraclels: Stopping fault monitor using pmfadm tag ORALSNR_MON_oraclels
Sep 28 14:17:52 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Stopping listener oracle.
Sep 28 14:17:52 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Using method 'run_setuid_prog' to execute shutdown commands
Sep 28 14:18:00 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Listener oracle stopped successfully
Sep 28 14:18:02 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Starting listener oracle.
Sep 28 14:18:02 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Using method 'run_setuid_prog' to execute start commands
Sep 28 14:18:06 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Listener oracle started.
Sep 28 14:18:08 SC[SUNWscor.oracle_listener.monitor_start]:oracle:oraclels: Starting monitor

Thanks for the reply Thorsten. The logs I included in the original post are actually from /var/opt/SUNWscor/oracle_listener/messages_log.$RESOURCE. I'd like to bump up the verbosity on the oracle_listener logs like I can with the oracle_server logs, but for whatever reason there is no debug_level parameter for the oracle_listener resource type. Sounds like I may be SOL, but thought I'd check with the forum and verify.

Set Logging level for my application

I've got an web-based application (ADF/EJB) and I'm trying to configure the logging level.
I'm using the Java Logging API and no matter what I change, short of hardcoding a call in to set the global logging level, I can't alter what level it is using. I've tried changing in the WebLogic console and all that does is change the logging level for WebLogic. I've tried adding properties files but they don't seem to be read.
Any Ideas?

Hey Mark,
I have no idea if this will help, but I was wanting to print out only my DML operations on commit and I got this post on my thread.
You could probably do this with -Djbo.debugoutput=adflogger and then fuss with the logging configuration, or perhaps by turning on JDBC loggingDouble-click your View Controller project-> Run/Debug/Profile -> Edit ,and then type the -Djbo.debugoutput=adflogger into your Java Options, but I don't know anything after that.
Good luck.
Will

Where can I set the log level for the "Inbox log file" ?

From the Siebel 8 Bookshelf, it says :
"To set the level of the Inbox log file for troubleshooting
*In Siebel Tools, set the Log Level for the Inbox log file (Alias = InboxLog) to 5*."
But where exactly in Siebel Tools can I find that Log Level ? Which object does the Siebel bookshelf talk about ?

Hi,
Loglevels are not configured in Siebel Tools. You have to configure them with the siebel client. You can find a parameter at "Administration - Server Configuration / Server / Events"
Search for "Inbox General Log Events". Set this parameter to 5. It think this should help you.
Cheers Andreas

Increasing log level for saw.log

Hi
Please let me know the steps to increase the logging level for saw.log
Thanks.

In the enterprise manager goto:
Business Intelligence >> coreapplication >> Diagnostics >> Log Configuration
Regards
John
http://obiee101.blogspot.com
http://obiee11g.com

OC4J: log level for application deployment?

Hi,
i have a application that can be deploy to co4j in window xp but not in AIX, and
the error message print is not so helpful.
i want to get more detail information about the error. (print more detail debug message)
Is there something like -Dxxx=debug to set the log level for application deployment?
thank you.

Most likely application is trying to display a prompt, run your app in full visibility mode and see if it goes through.
Sometimes, when app is receiving incorrect license key it will also hang like that. The only way it's going to fail is once you run out of time, which by default is 120 minutes I think.
Other times, app needs mapped drive etc, there might be many more reasons.
SCCM logs will show you what is received from app. If nothing is received, then logs are useless and you need to use application level logging or take a look at windows logs (system and application) - they might be useful too.
As a last resort, you can use psexec and run installer as system account to mimic what SCCM is using and see if app installs or also takes its sweet time.

Set logging severity level for clustered servers

How can I set the logging severity level for clustered servers just once at the cluster level rather than one at a time at the server level?

I know the logging is server by server, but surely there is a way to configure the multiple servers with one change rather than one by one. We have 40 some servers in the cluster.

Transaction Isolation Level for EJB methods

L.S.
I just found out the in OC4J one can not set the transaction isolation level on ejb methods. Moreover one needs to revert to bean managed transaction (manual coding of the ALL transaction logic) to set the isolation level.
On entity beans one can only set the isolation level for the whole bean (not on individual methods), and in session beans there is no way at all to set the isolation level.
This is on shear contract to all other application servers I used before (there one can declaratively set the isolation level for a ejb method, both in session and in entitybean deployment descriptors)
Is it foreseen in a future release to include such a valuable feature will be provided by oc4j?
Note that I was VERY surprised that OC4J could not handle this (I checked the j2ee spec, but admittedly the spec is a little vague about this support and makes it vendor dependent. the j2ee spec does not mandate this, except for CMP entity beans, but includes some suggestions on this ability. But most other application servers implemented the ability)
Regadrs,
Erik

Hello Erik --
I think we met in Perth recently?
Anyway, your information is correct.
We can set the transaction isolation level for each entity bean, at the bean level. We don't have for the specification of method level isolation settings -- I'd be interested to hear how you would like/do use this. What behaviour do you expect to see when a transaction is started that spans multiple methods on a bean with different declared isolation levels.
For session beans, we do not currently have the ability to declaratively specify the isolation level to use for the bean. I know this is not in the forthcoming 904 release, and will to check what is beyond that.
As you point out, this can be done programatically using the Connection.setIsolationLevel() method on any connections you are using from within the session bean.
I'd would like to log an enhancement request for you for this functionality. Can you send me an email at [email protected] and we'll take it offline.
-steve-

Schema level and table level supplemental logging

Hello,
I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command-
SQL>alter database add supplemental log data (primary key) columns;
Database altered.
SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;
SUPPLEME SUP SUP
IMPLICIT YES NO
-My question is should I enable supplemental logging table level also(for DML replication only)? should I run the below command also?
GGSCI (db1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
Successfully logged into database.
GGSCI (db1) 2> ADD TRANDATA schema.<table-name>
what is the deference between schema level and table level supplemental logging?

For Oracle, ADD TRANDATA by default enables table-level supplemental logging. The supplemental log group includes one of the following sets of columns, in the listed order of priority, depending on what is defined on the table:
1. Primary key
2. First unique key alphanumerically with no virtual columns, no UDTs, no functionbased
columns, and no nullable columns
3. First unique key alphanumerically with no virtual columns, no UDTs, or no functionbased
columns, but can include nullable columns
4. If none of the preceding key types exist (even though there might be other types of keys
defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
the database allows to be used in a unique key, excluding virtual columns, UDTs,
function-based columns, and any columns that are explicitly excluded from the Oracle
GoldenGate configuration.
The command issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA clause that
is appropriate for the type of unique constraint (or lack of one) that is defined for the table.
When to use ADD TRANDATA for an Oracle source database
Use ADD TRANDATA only if you are not using the Oracle GoldenGate DDL replication feature.
If you are using the Oracle GoldenGate DDL replication feature, use the ADD SCHEMATRANDATA command to log the required supplemental data. It is possible to use ADD
TRANDATA when DDL support is enabled, but only if you can guarantee one of the following:
● You can stop DML activity on any and all tables before users or applications perform DDL on them.
● You cannot stop DML activity before the DDL occurs, but you can guarantee that:
❍ There is no possibility that users or applications will issue DDL that adds new tables whose names satisfy an explicit or wildcarded specification in a TABLE or MAP
statement.
❍ There is no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.
ADD SCHEMATRANDATA ensures replication continuity should DML ever occur on an object for which DDL has just been performed.
You can use ADD TRANDATA even when using ADD SCHEMATRANDATA if you need to use the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters.
Additional requirements when using ADD TRANDATA
Besides table-level logging, minimal supplemental logging must be enabled at the database level in order for Oracle GoldenGate to process updates to primary keys and
chained rows. This must be done through the database interface, not through Oracle GoldenGate. You can enable minimal supplemental logging by issuing the following DDL
statement:
SQL> alter database add supplemental log data;
To verify that supplemental logging is enabled at the database level, issue the following statement:
SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
The output of the query must be YES or IMPLICIT. LOG_DATA_MIN must be explicitly set, because it is not enabled automatically when other LOG_DATA options are set.
If you required more details refer Oracle® GoldenGate Windows and UNIX Reference Guide 11g Release 2 (11.2.1.0.0)

Access level for Tab

Hi,
How can i define security level for each tab?
i have set of users and i want a particular tab to be displayed to certain users only not to all users.
i have already defined access privilege for the particular tab in the Advance option for tab granting privilege to specific user and also specified that this particular tab should not inherit privilege from the page, but still the tab is displayed to all the users.
regards,
Sunil
null

I also have this problem. I am using Portal 10.1.2.0.2.
I've set up two groups (systema_users and systemb_users) and have set up two tabs, each of which should be only accessible to one of these groups. However, no matter which user I log in as, I can see both tabs regardless of which group the user belongs to. On each tab I have set access to 'Specify Access Settings' and have specified the appropriate group, with the Customize Portlets (Full) privilege, since I need them to be able to customise the content of the tab. What am I missing here?

How to control listener log levels with log.xml

I'm running Oracle 11 and I am seeing tons of log.xml files being created, rotated, and renamed. Looking at the log.xml files, I'm seeing what appears to be rather excessive logging. It appears to be logging every single connection. Is there any way to control the logging levels for this file and/or decrease the number of log files kept in the rotation?

I don't believe it is possible to disable part of the ADR activity. But I would be interested in your definition of "excessive logging."
Are you seeing a specific performance impact or are you just seeing something different from 10gR2 (meaning the new ADR functionality)?

Specific Level for Log

Similar Messages

Maybe you are looking for