File system logs are Full

In my Database and Application Server,
mount point /sapmnt/D01/global
WF_LOG_000000016002_017-rwxrwxrwx   1 root       sys           2936 Jun 22 2007
WF_LOG_000000016003_017-rwxrwxrwx   1 root       sys           2936 Jun 22 2007
WF_LOG_000000016004_017-rwxrwxrwx   1 root       sys           2936 Jun 22 2007
WF_LOG_000000016005_017-rwxrwxrwx   1 root       sys           2936 Jun 22 2007
WF_LOG_000000016006_017-rwxrwxrwx   1 root       sys          26225 Jun 22 2007
WF_LOG_000000066004_017-rwxrwxrwx   1 root       sys           5548 Jun 22 2007
WF_LOG_000000066005_017-rwxrwxrwx   1 root       sys          29140 Jun 22 2007
WF_LOG_000000066006_017-rwxrwxrwx   1 root       sys          24134 Jun 22 2007
So shall I remove this logs frm database and Application Server.
Regards,
santosh

Thanx SAM, for reply message, I use swu10 remove the log.
but in my file system is still showing 93 % full.
/sampmt/D01/global      following direcory are there .
total 15730
drwxrwxrwx   2 root       sys         152576 Apr 16 10:35 000JOBLG
drwxrwxrwx   2 root       sys         432128 Apr 16 18:56 017BDCLG
drwxrwxrwx   2 root       sys        4234240 Apr 17 09:50 017JOBLG
-rwxrwxrwx   1 root       sys              0 Jun 22 2007 ABAPPROT
-rw-rr   1 d01adm     sapsys      416440 Apr 17 09:48 SLOGJ
-rwxrwxrwx   1 root       sys         639432 Jun 24 2007 SLOGJ.SAV
-rw-rr   1 d01adm     sapsys      999920 Apr 14 10:27 SLOGJO
-rwxrwxrwx   1 d01adm     sapsys      999920 Jun 23 2007 SLOGJO.SAV
-rw-rw----   1 d01adm     sapsys        2515 Apr 15 12:35 WF_LOG_000000125004_017
-rwxrwxrwx   1 d01adm     sapsys         160 Jun 25 2007 dev_sapstart
-rwxrwxrwx   1 d01adm     sapsys         270 Jun 24 2007 ms_acl_info
drwxrwxrwx   2 d01adm     sapsys        1024 Apr 13 09:26 sapcontrol
drwxrwxrwx   4 d01adm     sapsys          96 Jun 24 2007 security
pwd
/sapmnt/D01/global
shall I remove this logs directory..
Regards,
Santosh

Similar Messages

Whether will falsh player support Unrestricted File System Access in Full Trust ?if it will , when?

    I am doing a software based on Flash , to provide my customer to edit pictures online.
    In some scenario, to get Full Acess Local File is necessary. I find SliverLight 5.0 had supported such features:
Unrestricted File System Access in Full Trust
Full Trust in-browser for enterprise scenarios
Default Filename in SaveFileDialog and OpenFileDialog
   I really desire those features , so , I am wondering whether adobe will support it .If will, when?

Please read the below flash player administrator guide
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/flashplayer/pdfs/flas h_player_11_7_admin_guide.pdf
check the section "The User FlashPlayerTrust directory". It will help.

File system is getting full Frequently in Federated Portal

Hi
In my production federated portal the file system
File system /usr/sap/<SID>/JC01 -
is getting full 100% for every 30 minutes ,
what could be the reason for this behavior, this is happening since from 6 days
can I be assisted on this
Regards

Hi Michael ,
It does not release the space automatically, what does this command show du -k | sort -n Following are the last lines
I pasted the lines vertically , but in this page all lines are mixed and clubbed horizontally the out put of the command start now ************************************
214260 ./j2ee/cluster/server0/temp/webdynpro
214660 ./SDM/root/origin/sap.com/caf
214704 ./SDM/root/origin/com.adobe/PDFManipulation/Adobe Systems/0/800.20070626144044.156488
217212 ./j2ee/cluster/server0/temp
223168 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps
224000 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps
225844 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal
226672 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal
227456 ./j2ee/cluster/dispatcher/log
233540 ./SDM/root/origin/com.adobe/FontManagerService
233540 ./SDM/root/origin/com.adobe/FontManagerService/Adobe Systems
233540 ./SDM/root/origin/com.adobe/FontManagerService/Adobe Systems/0
262300 ./j2ee/cluster/dispatcher
283464 ./SDM/root/origin/sap.com/ess
292296 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/deployment
295108 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/portalapps
295324 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/portalapps
300344 ./j2ee/cluster/server1/temp/webdynpro/temp
300344 ./j2ee/cluster/server1/temp/webdynpro/temp/sap.com
350848 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root/web-inf
351096 ./exe
366616 ./SDM/root/origin/com.adobe/XMLFormService
366616 ./SDM/root/origin/com.adobe/XMLFormService/Adobe Systems
366616 ./SDM/root/origin/com.adobe/XMLFormService/Adobe Systems/0
383428 ./SDM/program
388232 ./SDM/root/origin/sap.com/tc
487640 ./j2ee/cluster/server1/temp/webdynpro
490564 ./j2ee/cluster/server1/temp
508248 ./j2ee/os_libs/adssap
519288 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf
567240 ./SDM/root/origin/com.adobe/PDFManipulation
567240 ./SDM/root/origin/com.adobe/PDFManipulation/Adobe Systems
567240 ./SDM/root/origin/com.adobe/PDFManipulation/Adobe Systems/0
645996 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj/root
650780 ./j2ee/cluster/server1/apps/sap.com/irj
650780 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp
650780 ./j2ee/cluster/server1/apps/sap.com/irj/servlet_jsp/irj
723796 ./j2ee/os_libs
814652 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root
819436 ./j2ee/cluster/server0/apps/sap.com/irj
819436 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp
819436 ./j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj
1248364 ./SDM/root/origin/com.adobe
1319004 ./j2ee/cluster/server1/apps/sap.com
1336304 ./j2ee/cluster/server1/apps
1470012 ./j2ee/cluster/server0/log/archive
1665496 ./j2ee/cluster/server1/log/archive
1681300 ./SDM/root/origin/sap.com
1730984 ./j2ee/cluster/server0/log
1856844 ./j2ee/cluster/server0/apps/sap.com
1878272 ./j2ee/cluster/server0/apps
1927368 ./j2ee/cluster/server1/log
2929664 ./SDM/root/origin
2931364 ./SDM/root
3314792 ./SDM
3881168 ./j2ee/cluster/server1
3943000 ./j2ee/cluster/server0
8094976 ./j2ee/cluster
9156032 ./j2ee
12878604 .
*****************end of out put
Regards
Edited by: sidharthmellam on Oct 27, 2009 4:15 AM

DB2 logs are full

Hi All,
We install SRM system with DB2 9.1, We have using logarchmeth1. The log directory /db2/SID/log_dir is getting full every time.
We are taking full online backup including logs every week for the Development server.
Can i delete the logs in the log_dir..? as we are taking full online backup including logs. And we dont have tape to take backup of archive logs.
Please suggest..
Regards,
Sreekanth

Hi All,
Please find the db2 config parameters below. please suggest is it ok or need to change any thing.
H:\db2\db2srd\db2_software\BIN>db2 get db cfg for SRD
       Database Configuration for Database SRD
Database configuration release level                    = 0x0b00
Database release level                                  = 0x0b00
Database territory                                      = en_US
Database code page                                      = 1208
Database code set                                       = UTF-8
Database country/region code                            = 1
Database collating sequence                             = IDENTITY_16BIT
Alternate collating sequence              (ALT_COLLATE) =
Database page size                                      = 16384
Dynamic SQL Query management           (DYN_QUERY_MGMT) = DISABLE
Discovery support for this database       (DISCOVER_DB) = ENABLE
Restrict access                                         = NO
Default query optimization class         (DFT_QUERYOPT) = 5
Degree of parallelism                      (DFT_DEGREE) = 1
Continue upon arithmetic exceptions   (DFT_SQLMATHWARN) = NO
Default refresh age                   (DFT_REFRESH_AGE) = 0
Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
Number of frequent values retained     (NUM_FREQVALUES) = 10
Number of quantiles retained            (NUM_QUANTILES) = 20
Backup pending                                          = NO
Database is consistent                                  = NO
Rollforward pending                                     = NO
Restore pending                                         = NO
Multi-page file allocation enabled                      = YES
Log retain for recovery status                          = NO
User exit for logging status                            = YES
Self tuning memory                    (SELF_TUNING_MEM) = ON
Size of database shared memory (4KB) (DATABASE_MEMORY) = 2795520
Database memory threshold               (DB_MEM_THRESH) = 10
Max storage for lock list (4KB)              (LOCKLIST) = AUTOMATIC
Percent. of lock lists per application       (MAXLOCKS) = AUTOMATIC
Package cache size (4KB)                   (PCKCACHESZ) = AUTOMATIC
Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = AUTOMATIC
Sort list heap (4KB)                         (SORTHEAP) = AUTOMATIC
Database heap (4KB)                            (DBHEAP) = 25000
Catalog cache size (4KB)              (CATALOGCACHE_SZ) = 2560
Log buffer size (4KB)                        (LOGBUFSZ) = 1024
Utilities heap size (4KB)                (UTIL_HEAP_SZ) = 10000
Buffer pool size (pages)                     (BUFFPAGE) = 10000
Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 128000
Percent of mem for appl. group heap   (GROUPHEAP_RATIO) = 25
Max appl. control heap size (4KB)     (APP_CTL_HEAP_SZ) = 1600
SQL statement heap (4KB)                     (STMTHEAP) = 5120
Default application heap (4KB)             (APPLHEAPSZ) = 4096
Statistics heap size (4KB)               (STAT_HEAP_SZ) = 15000
Interval for checking deadlock (ms)         (DLCHKTIME) = 10000
Lock timeout (sec)                        (LOCKTIMEOUT) = 3600
Changed pages threshold                (CHNGPGS_THRESH) = 40
Number of asynchronous page cleaners   (NUM_IOCLEANERS) = AUTOMATIC
Number of I/O servers                   (NUM_IOSERVERS) = AUTOMATIC
Index sort flag                             (INDEXSORT) = YES
Sequential detect flag                      (SEQDETECT) = YES
Default prefetch size (pages)         (DFT_PREFETCH_SZ) = 32
Track modified pages                         (TRACKMOD) = ON
Default number of containers                            = 1
Default tablespace extentsize (pages)   (DFT_EXTENT_SZ) = 2
Max number of active applications            (MAXAPPLS) = AUTOMATIC
Average number of active applications       (AVG_APPLS) = AUTOMATIC
Max DB files open per application            (MAXFILOP) = 1950
Log file size (4KB)                         (LOGFILSIZ) = 16380
Number of primary log files                (LOGPRIMARY) = 20
Number of secondary log files               (LOGSECOND) = 40
Changed path to log files                  (NEWLOGPATH) =
Path to log files                                       = H:\db2\SRD\log_dir\NO
DE0000\
Overflow log path                     (OVERFLOWLOGPATH) =
Mirror log path                         (MIRRORLOGPATH) =
First active log file                                   = S0002249.LOG
Block log on disk full                (BLK_LOG_DSK_FUL) = YES
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
Group commit count                          (MINCOMMIT) = 1
Percent log file reclaimed before soft chckpt (SOFTMAX) = 300
Log retain for recovery enabled             (LOGRETAIN) = OFF
User exit for logging enabled                (USEREXIT) = OFF
HADR database role                                      = STANDARD
HADR local host name                  (HADR_LOCAL_HOST) =
HADR local service name                (HADR_LOCAL_SVC) =
HADR remote host name                (HADR_REMOTE_HOST) =
HADR remote service name              (HADR_REMOTE_SVC) =
HADR instance name of remote server (HADR_REMOTE_INST) =
HADR timeout value                       (HADR_TIMEOUT) = 120
HADR log write synchronization mode     (HADR_SYNCMODE) = NEARSYNC
First log archive method                 (LOGARCHMETH1) = DISK:H:\db2\SRD\log_d
ir\NODE0000\
Options for logarchmeth1                  (LOGARCHOPT1) =
Second log archive method                (LOGARCHMETH2) = OFF
Options for logarchmeth2                  (LOGARCHOPT2) =
Failover log archive path                (FAILARCHPATH) =
Number of log archive retries on error   (NUMARCHRETRY) = 5
Log archive retry Delay (secs)         (ARCHRETRYDELAY) = 20
Vendor options                              (VENDOROPT) =
Auto restart enabled                      (AUTORESTART) = ON
Index re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)
Log pages during index build            (LOGINDEXBUILD) = OFF
Default number of loadrec sessions    (DFT_LOADREC_SES) = 1
Number of database backups to retain   (NUM_DB_BACKUPS) = 12
Recovery history retention (days)     (REC_HIS_RETENTN) = 60
TSM management class                    (TSM_MGMTCLASS) =
TSM node name                            (TSM_NODENAME) =
TSM owner                                   (TSM_OWNER) =
TSM password                             (TSM_PASSWORD) =
Automatic maintenance                      (AUTO_MAINT) = ON
   Automatic database backup            (AUTO_DB_BACKUP) = OFF
   Automatic table maintenance          (AUTO_TBL_MAINT) = ON
     Automatic runstats                  (AUTO_RUNSTATS) = ON
     Automatic statistics profiling    (AUTO_STATS_PROF) = OFF
       Automatic profile updates         (AUTO_PROF_UPD) = OFF
     Automatic reorganization               (AUTO_REORG) = OFF
And i have cut and pasted the old logs to another location.
Regards,
Sreekanth

Root file system is 100% full on server with oracle databse

hi,
This was very strange to me, i have a solaris 10 Generic_122300-03 sun4u sparc SUNW,Sun-Fire-V440, with one oracle database running on it. The daatabase guys was doing some activity and the CPU utilization was 100%. I got an update from db team that their process was hung for aroung 2 hours and db was not coming up. At this point of time the / file system was piling 100% and suddenly the database came up and / file system came down to normal.
i am not sure what had happened, i didnt get an oppurtunity to check for any logs files getting generated under / apart from var or swap which can cause this. var is seperate file system.
any idea on finding this out?

Only thing I can suggest is to have auditing enabled - then you can possibly see what file or directories are being accessed during this time when it slows down. Also make sure you have enough swap space defined. I had production machines in the past that generated massive swap usage and the system would slow to a crawl during the time the application/machine was initializing for a run. Also check the usual messages in /var/adm.

The system log is full with this !!! Can you help me?

Hi gurus, please, I need your help.
Our log is fulled with an error ( I mean aroung 10 MB of logs with the same error)
Please, !! We are in SP15 EP 7.0
java.util.zip.ZipException: error in opening zip file
 at java.util.zip.ZipFile.open(Native Method)
 at java.util.zip.ZipFile.<init>(ZipFile.java:111)
 at java.util.zip.ZipFile.<init>(ZipFile.java:127)
 at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchiveInfo(AbstractLog.java:328)
 at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:455)
 at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:478)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
 at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
 at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
 at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
 at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
 at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
 at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
 at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
 at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfo(LogControllerFacade.java:227)
 at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfosWithPattern(LogControllerFacade.java:193)
 at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfos(LogControllerFacade.java:174)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
 at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
 at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
 at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
 at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
 at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
 at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
 at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.tc.logviewer.mbean.LocalLVMBeanServer.invoke(LocalLVMBeanServer.java:73)
 at $Proxy165.getAttribute(Unknown Source)
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getAttribute(AbstractLogDepot.java:236)
 at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getLogDescriptors(AbstractLogDepot.java:84)
 at com.sap.tc.logviewer.mbean.ServerModelLogDepot.getLogDescriptors(ServerModelLogDepot.java:79)
 at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup$GetLogDescriptorsTask.run(ServerModelLogDepotGroup.java:60)
 at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.execute(ServerModelLogDepotGroup.java:173)
 at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.getLogDescriptors(ServerModelLogDepotGroup.java:119)
 at com.sap.tc.logviewer.mbean.LogviewerServer.getLogs(LogviewerServer.java:137)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
 at javax.management.StandardMBean.invoke(StandardMBean.java:286)
 at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
 at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
 at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
 at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
 at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
 at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
 at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)
 at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
 at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerInvoker.invoke(J2EELogviewerServerInvoker.java:111)
 at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerProxy.getLogs(J2EELogviewerServerProxy.java:105)
 at com.sap.tc.logviewer.client.base.LogviewerClientImpl.getLogs(LogviewerClientImpl.java:114)
 at com.sap.lm.webadmin.logviewer.impl.LV_View.getLogs(LV_View.java:865)
 at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchLogs(LV_View.java:834)
 at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:516)
 at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:496)
 at com.sap.lm.webadmin.logviewer.impl.LV_View.fetchView(LV_View.java:492)
 at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:609)
 at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:577)
 at com.sap.lm.webadmin.logviewer.impl.LVUI.openView(LVUI.java:573)
 at com.sap.lm.webadmin.logviewer.LVView.onActionOpenSingleView(LVView.java:1648)
 at com.sap.lm.webadmin.logviewer.wdp.InternalLVView.wdInvokeEventHandler(InternalLVView.java:1560)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks in advance

Hi,
have you take a look at SAP Note 701330 ?
One thread looking like your problem :
Re: error in opening zip file after Patch 4 HF6 install
Fabien.

File system log files for SOA Gateway

Hi All,
I need to get log files for my integration repository/SOA Gateway since I'm not able to generate any WSDL or to deploy a web service. In the SOA trouble shoot document, it says:
Log on to Oracle E-Business Suite with the username that has the System Administrator responsibility access privilege.
Select the System Administrator responsibility from the Navigator and choose Oracle Applications Manager > Logs.
Click Log Setup to open the Java System Property Settings page.
Click the Site link and enable log for
Midtier Log File Name: Enter the file name that you would like on the middletier, for example, '/tmp/SOA /tmp/SOALog.log'.
Module=Enter an appropriate module name, for example, 'fnd.soa%'.
Ask your System Administrator to bounce oafm container.
Perform any SOA specific action, such as generate a WSDL file for an PL/SQL API.
Look for logs in the file specified in the Midtier Log File Name field.
My problem is, that my EBS installation is running on windows, so '/tmp/SOA /tmp/SOALog.log' will not work, right? I tried something like /temp/... or c:/temp/... or c:\temp\... but I did not get a logfile called SOALog.log.
What do I have to provide as path here?
Many thanks,
Konrad

Hi!
Did you encounter any error?Yes!
>
try givng C:\temp remember temp should have read and write permissions for the oracle applications o/s user(applmgr)Using c:\temp\test.log results in the following error while saving the log setting:
An error has occurred!
For input string: "10001:\temp\test.log"
I can use whatever string I want, but as long as a ":" is included, I get that error.
As for the user permissions. I installed the EBS using the standard Administrator account and this account is a member of Administrators and ora_dba.
Best,
Konrad

Problem with file system logging in Solaris7

Hi,
Solaris7 by default provides filesystem logging option. I mount a filesystem with "-o logging" option and then crash the filesystem. Next time i am able to mount the same filesystem without having to do an fsck.
But the same does not happen if i mount the filesystem with mount(2) system call with the flag MNTOPT_LOGGING. Sample code is below
--------------Ex code ---------------
struct ufs_args ufs_mount;
ufs_mount.flags = UFSMNT_LARGEFILES|UFSMNT_LOGGING;
length = sizeof(ufs_mount);
mount(dev,mntpoint[i],MS_DATA,filesys,(char *)&ufs_mount,length);
I could avoid this by following the below steps:
1. mount the required filesystem with mount(1) command
mount -o logging /dev/dsk/c1t5d0s0 /mnt
2. Do some activity on it. ex cp,rm and then unmount.
3. Now use the mount(2)system call and mount the filesystem(above prog).
After following these steps even if the filesystem crashed it can be mounted next time with the mount(2) system call without an fsck(1).
I have also observed that a filesystem mounted using mount(2) call very frequently gives a "ufs log error , errno = 5" and needs an fsck after very few crashes.
I have tried this on both 32 & 64 bit Solaris7.
thanks in advance,
rakesh.

Hi,
Solaris7 by default provides filesystem logging option. I mount a filesystem with "-o logging" option and then crash the filesystem. Next time i am able to mount the same filesystem without having to do an fsck.
But the same does not happen if i mount the filesystem with mount(2) system call with the flag MNTOPT_LOGGING. Sample code is below
--------------Ex code ---------------
struct ufs_args ufs_mount;
ufs_mount.flags = UFSMNT_LARGEFILES|UFSMNT_LOGGING;
length = sizeof(ufs_mount);
mount(dev,mntpoint[i],MS_DATA,filesys,(char *)&ufs_mount,length);
I could avoid this by following the below steps:
1. mount the required filesystem with mount(1) command
mount -o logging /dev/dsk/c1t5d0s0 /mnt
2. Do some activity on it. ex cp,rm and then unmount.
3. Now use the mount(2)system call and mount the filesystem(above prog).
After following these steps even if the filesystem crashed it can be mounted next time with the mount(2) system call without an fsck(1).
I have also observed that a filesystem mounted using mount(2) call very frequently gives a "ufs log error , errno = 5" and needs an fsck after very few crashes.
I have tried this on both 32 & 64 bit Solaris7.
thanks in advance,
rakesh.

Root file system getting full SLES 10 SAP ERP6

Hi Gurus
Iam having an unusual problem.My / file system is getting full and i can`tv pick up what causing it .I have checked the logs in /var/messages.I dont know whats writing to / .I didnt copy anything directly on /
Filesystem            Size Used Avail Use% Mounted on
/dev/sda5             7.8G 7.5G     0 100% /
SLES 10 64 bit ERP6 SR2
Anyone who had a similar problem.
Any ideas are welcome

cd /
xwbr1:/ # du -hmx --max-depth=1
1       ./lost+found
48      ./etc
1       ./boot
1       ./sapdb
1       ./sapmnt
1430    ./usr
0       ./proc
0       ./sys
0       ./dev
85      ./var
8       ./bin
1       ./home
83      ./lib
12      ./lib64
1       ./media
1       ./mnt
488     ./opt
56      ./root
14      ./sbin
2       ./srv
1       ./tmp
1       ./sapcd
1       ./backupdisk
1       ./dailybackups
1       ./fulloffline
cd /root
xwbr1:~ # du -hmx --max-depth=1
1       ./.gnupg
1       ./bin
1       ./.kbd
1       ./.fvwm
2       ./.wapi
12      ./dsadiag
1       ./.gconf
1       ./.gconfd
1       ./.skel
1       ./.gnome
1       ./.gnome2
1       ./.gnome2_private
1       ./.metacity
1       ./.gstreamer-0.10
1       ./.nautilus
1       ./.qt
1       ./Desktop
1       ./.config
1       ./Documents
1       ./.thumbnails
38      ./.sdtgui
1       ./sdb
1       ./.sdb
4       ./.mozilla
56      .

File system getting full and Server node getting down.

Hi Team,
Currently we are using IBM Power 6 AIX operating system.
And in our environment, for development system, file system is getting full and development system is getting slow while accessing.
Can you please let me know , what exactly the problem & which command is used to see the file system size and how to resolve the issue by deleting the core files or some ting. Please help me .
Thanks
Manoj K

Hi Orkun Gedik,
When i executed the command df -lg and find . -name core noting is displayed, but if i execute the command df is showed me the below information. below is an original file which i have modified the sid.
Filesystem 512-blocks Free %Used Iused %Iused Mounted on
/dev/fslv10 52428800 16279744 69% 389631 15% /usr/sap/SID
Server 0 node is giving the problem. its getting down all the times.
And if i check it in the /usr/sap/SID/<Instance>/work for the server node "std_server0.out file , the below information is written in the file.
framework started for 73278 ms.
SAP J2EE Engine Version 7.00 PatchLevel 81863.450 is running! PatchLevel 81863.450 March 10, 2010 11:48 GMT
94.539: [GC 94.539: [ParNew: 239760K->74856K(261888K), 0.2705150 secs] 239760K->74856K(2009856K), 0.2708720 secs] [Times: user=0.00 sys=0.36, real=0.27 secs]
105.163: [GC 105.164: [ParNew: 249448K->80797K(261888K), 0.2317650 secs] 249448K->80797K(2009856K), 0.2320960 secs] [Times: user=0.00 sys=0.44, real=0.23 secs]
113.248: [GC 113.248: [ParNew: 255389K->87296K(261888K), 0.3284190 secs] 255389K->91531K(2009856K), 0.3287400 secs] [Times: user=0.00 sys=0.58, real=0.33 secs]
Please advise.
thanks in advance
Manoj K

Huge System.log and asl files. Can these be deleted? What may be the casue?

Following on from an earlier posting regarding disappearing disk space, a couple of responses suggested running a disk utility such as OmniDiskSweeper.
I ran this and it highlighted that the private folder, specifically 'private/var/log' is taking up almost 49 GB! There are 2 system log files:
system.log.0 is almost 20 GB and system.log is close to 19 GB and a file, asl is 10 GB
What are these, can they be deleted, and what may have caused them to be so large in the first place?

This was being written repeatedly to the system.log file. I removed the application, restarted the Mac and the problem appears to be resolved
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * _NSAutoreleaseNoPool(): Object 0x25ad980 of class NSCFString autoreleased with no pool in place - just leaking\nStack: (0x939f6dac 0x93923e14 0x9394ff04 0xb0007438 0xb0004b8c 0xc054 0xc618 0x7000e7c8 0x7000dda8 0x7000cf64 0x90358c10 0x903587d4 0x90358718 0x903abb88 0x903582f4 0x90358464 0x903582f4 0x9036dd48 0x7000cad0 0x70005d04 0x7001140c 0x924d6624 0x924d62b0 0x924d6164 0x924d4b34 0x924d47f4 0x924c2de8 0x9232b0c8)
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * -[NSConditionLock unlockWithCondition:]: lock (<NSConditionLock: 0x12c2c0> '(null)') unlocked when not locked
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * Break on _NSLockError() to debug.

Can we store ORACLE DATA and LOG files in seperate file system

I am installing NW2004s in HP UNIX Server with Oracle database
I have selected the option as custom
I would want the SAP datafiles to be stored in /sapdata file system
Log files to be stored in /oraclelog file system
While installation SAP is just asking me for the location of SAP data files. It is not asking me for the location of the log files.
(It is asking me for the location of control files)
Hence as per my understanding the oracle log files can be saved only in the same directory as oracle Data file.
Please confirm

I have heard reports of people that made some kind of synchronization between AD and OID, but I have no hands on experience with this. There are some notes on metalink that describe the process, but I try to stay away from AD as far as possible (I usually work on unix or linux environments and those don't really mix with AD).

In rz20 all file systems are not coming.

Hi all.
I have ccms configuration in local system not in central system menas every system there are own ccms configuration.
File system In rz20 that all file systems are not coming.
in os level there are like sapdata1,sapdata2.... & sapreorg but these file system are not coming in rz20.so we are not getting any alert regarding this file systems.
Kindly suggest how can i fetch all the file system which are available in os level.
thanks in advance.
Thanks & regards,
Laxmid

Hi Kumar,
Os -HP Unix
In *RZ0> SAP CCMS Monitor Templates>Filesystems--->* these below file systems are not coming.Otheres are coming.
/oracle/RXN/sapdata1
/oracle/RXN/sapdata2
/oracle/RXN/sapdata3
/oracle/RXN/sapdata4
/oracle/RXN/oraarch
/oracle/RXN/sapreorg
& please tell me there is one Lock & unlock is there in front of every node.what is this.
Thanks & Regards
Laxmi
Edited by: laxmid on Feb 7, 2010 9:04 PM

System Log file filled with arp message from teamed nics

Hello,
We are running a Win2k3 server with dual nics teamed to one IP address. All of our Mac's system logs are being filled with the following message:
Mar 28 12:48:58 Son-of-Spacedog kernel[0]: arp: 192.168.200.50 moved from 00:04:23:b9:00:4a to 00:04:23:b9:00:4b on en0
This is repeated over and over. Is there any way to get the Mac's to stop generating this message? Is the fix for this on the server side or on the Mac side? From what I have seen online in other forums, this started happening with Panther.

There are actually several different types of NIC Teaming Modes:
Adapter Fault Tolerance (AFT) - provides automatic redundancy for a server's network connection. If the primary adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports two to eight adapters per team. This teaming mode works with any hub or switch, and all team members must be connected to the same device.
Switch Fault Tolerance (SFT) - provides a failover relationship between two adapters when each adapter is connected to a separate switch. Switch Fault Tolerance supports two adapters per team. This feature works with any switch. Spanning Tree Protocol (STP) must be enabled when you create a team in SFT mode.
Adaptive Load Balancing (ALB) - provides load balancing for transmission traffic and adapter fault tolerance. You can also enable or disable receive load balancing (RLB) in ALB teams. This teaming mode works with any switch.
Fast EtherChannel/Link Aggregation - provides increased transmission and reception throughput in a team of two to eight adapters. This mode also includes adapter fault tolerance and load balancing (only routed protocols). This requires a switch with Link Aggregation or FEC capability.
Gigabit EtherChannel/Link Aggregation - is the gigabit extension of the FEC/Link Aggregation/802.3ad: static mode. All team members must operate at gigabit speed.
IEEE 802.3ad: dynamic mode - creates one or more teams using dynamic Link Aggregation with same-speed or mixed-speed adapters. Like the static Link Aggregation modes, Dynamic 802.3ad teams increase transmission and reception throughput and provide fault tolerance. This mode requires a switch that fully supports the IEEE 802.3ad standard.
Now, most likely, somewhere on the network a server is configured for ALB or AFT, and these are the most common methods of NIC teaming (Sadly, the XServes do not). They also do not require any certain type of switch, but they do require STP (Spanning Tree Protocol) to be turned off to function most effectively, or you will see errors on the network like the ones you are seeing in your log. Most managed switches come with STP turned on by default, so you will need to check ALL switches (as the errors will cascade throughout the network) to see if it STP is turned on. Most people do not use STP any more (it basically allows ports on one switch to appear as on another switch), so see if you can turn it off. That should stop the error messages.
-MacBoy in SLC
PowerMac G5 Dual 2.0 GHz Mac OS X (10.4.6)

Lots of error in server's system log

I just installed SAPNetWeaver04_SP16Preview in a fresh Windows 2003 SP1. I am running it in VMware 1.0.3. I assigned VM 924MB RAM, 32GB hard drive and 2 Processors. Running JDK 1.4.2_09
After installation, I start the J2E from SAP Management Console. After the server is completely running. I look at the log (\usr\sap\J2E\JC00\j2ee\cluster\server0\log\system\logging.0.log). It is 1600KB now. I see a lot of similar errors. They are all from com.sap.tc.logging.FileLogInfoData
I post the very first one here
#1.5#000C299515C5000F0000000000000A4C000430B464E10B63#1179451251588#/System/Logging##com.sap.tc.logging.FileLogInfoData.[getFileHeader(String fileName, int cntHeadLines)]#######SAPEngine_System_Thread[impl:5]_93##0#0#Warning##Java#SAP_LOGGING_UNEXPECTED##Unexcepted error occured on {0}!#1#FileHeader parsing#
#1.5#000C299515C5000F0000000100000A4C000430B464E11826#1179451251588#/System/Logging##/System/Logging#######SAPEngine_System_Thread[impl:5]_93##0#0#Path##Java###Caught {0}#1#java.lang.Exception: .\log\services\log_configurator\default.0.trc (The system cannot find the path specified)
 at com.sap.tc.logging.FileLogInfoData.getEOLLength(FileLogInfoData.java:432)
 at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:348)
 at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:334)
 at com.sap.tc.logging.FileLogInfoData.loadFileLogHeader(FileLogInfoData.java:320)
 at com.sap.tc.logging.FileLogInfoData.init(FileLogInfoData.java:260)
 at com.sap.tc.logging.FileLogInfoData.<init>(FileLogInfoData.java:119)
 at com.sap.tc.logging.FileLog.init(FileLog.java:373)
 at com.sap.tc.logging.FileLog.<init>(FileLog.java:282)
 at com.sap.tc.logging.FileLog.<init>(FileLog.java:246)
 at com.sap.engine.services.log_configurator.admin.LogConfigurator.adjustConfiguration(LogConfigurator.java:665)
 at com.sap.engine.services.log_configurator.admin.LogConfigurator.applyConfiguration(LogConfigurator.java:1484)
 at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.activateLogger(LogConfiguratorServiceFrameImpl.java:225)
 at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:134)
 at com.sap.engine.services.log_configurator.LogConfiguratorApplicationServiceFrame.start(LogConfiguratorApplicationServiceFrame.java:51)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
The rest log are similar. They have different target file location. And they all throw at at com.sap.tc.logging.FileLogInfoData.getEOLLength(FileLogInfoData.java:432).
On the other side, I see an error from the log file ( C:\usr\sap\J2E\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc)
#1.5#000C299515C500390000003000000A4C000430B4667B0658#1179451278478#com.sapmarkets.bam.jmxadapter.util.LogDirectory##com.sapmarkets.bam.jmxadapter.util.LogDirectory#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###Error writing log directory entryC:\tmp\MARCH_J2E_00_6474950_lv_.xml (The system cannot find the path specified)#
#1.5#000C299515C500390000003200000A4C000430B4667B07B3#1179451278478#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register a new log#
#1.5#000C299515C500390000003400000A4C000430B4667B08D4#1179451278478#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: <--Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.#
#1.5#000C299515C500390000003600000A4C000430B4667B0D97#1179451278494#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###Originated from: com.sapmarkets.bam.util.BAMRuntimeException: <--Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.
 at com.sapmarkets.bam.jmxadapter.util.LogDirectory.write(LogDirectory.java:779)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.addToDirectory(AbstractFileLogHandler.java:361)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:249)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
 at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
 at com.sap.tc.logging.LoggingManager.addListener(LoggingManager.java:116)
 at com.sapmarkets.bam.jmxadapter.sapjlog.LogTypeConfiguratorImpl.configure(LogTypeConfiguratorImpl.java:98)
 at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypeConfigurators(MBeanRegistrar.java:106)
 at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypes(MBeanRegistrar.java:179)
 at com.sapmarkets.bam.jmx.connector.AbstractLVServer.init(AbstractLVServer.java:62)
 at com.sapmarkets.bam.j2ee.services.logviewer.LogViewer.start(LogViewer.java:158)
 at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
 at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Not sure if they are related. However, I don't have folder with is "C:\tmp\". I only have "C:\TEMP\". I checked the system variables, "%TEMP%" and "%TMP" are point to "%SystemRoot%\TEMP".
So how can I fix all exception in the logs. What should I look at first? My goal is to use SAP logging. I tried on the other system and what I got is similar error from FileLogInfoData. So I thought I may mess up the setting. I install on the fresh OS, I have no clue now. Any suggestion would help.

Hi,
1.Try using latest JDK,j2sdk1.4.2_13.
2.Check if environment variables JAVA_HOME and path are set correctly
3.Check if there is sufficient space in installation drive.
4.try connecting to database and see if data logs are full.remove unnecessary logs in database.
5.manually start all services through telnet or visual admin.
reward points if helpful.........

File system logs are Full

Similar Messages

Maybe you are looking for