Table index size in DB02 smaller after upgrade

SAP ERP 6.0, DB2 9.5, AIX 5.3. After we upgraded to SPS 15 / EHP4 / Netweaver EHP1 SPS02 using the downtime minimized method (shadow instance created) the index sizes for the tables are showing reduced sizes. When looking in DB02 under History -> "tables and indexes" all the tables show a drop in index sizes. I have compared the indexes to a pre upgrade copy of the system and all the indexes are still defined and active in the upgrades system. Can somebody please explain why the size drop? Is this a reporting error or what?

Hi Eddie,
DB2 V8.2 did not allow to retrieve table/index size information from DB2 directly. Therefore the SAP DB2 database interface and the CCMS code tried to do some size estimation based on cardinality and table/index width. DB2 V9.1+ provides table function ADMIN_GET_TAB_INFO to retrieve size information directly from DB2. Since this size information is much more accurate the SAP DB2 database interface and the CCMS code have been changed to use this table function.
So the phantom-"shrink" you observed may be related to the switch from size estimation to the size retrieved from ADMIN_GET_TAB_INFO . This may have happened directly after the V9.5 upgrade ( size retrieved differently in SAP DB2 database interface ) or after the SAP release upgrade ( change in CCMS ABAP coding ).
Regards
Frank

Similar Messages

Table/Index size

How do I find out the size of an existing table and an index ?
Thanks

analyze the table or index.
see dba_segments
dba_extents
where segmenT_type in ('TABLE','INDEX'
null

BWA Fact Table Index Size

Hi
Can anybody tell me how the BWA decides when a fact table index gets split into multiple parts? We have a number of very large cubes that are indexed and some have a fact table index that consists of one logical index which is made up of multiple physical indexes but other, similar sized cubes, just have one very large physical index for the fact table.
With the one very large physical index we seem to get an overload problem but when they are split into multiple parts we don't.
Thanks
Martin

Hi Martin,
this depends on the reorg config and the attribute of the index. You can manually trigger a splitting of an index via command 'ROUNDROBIN x', x stand for the number of parts which the index will be split to. Therefore you have to go into trexadmin standalone tool -> landscape right click on index -> split/merge index...
If you want an automatically split, you have to setup your reorg settings. Goto trexadmin standalone tool -> tab reorg -> options -> here you can choose the type of algorithm. Have a look into note 1313260 and 1163149.
Do you have a scheduled reorg job?
Regards,
Jens
PS: Every black box can be understood...

Aperture Library is now 20% smaller after upgrading to 3...should it be??

After upgrading my Aperture library to Aperture 3 it went from 117GB to 91GB. Does that seem correct??? Number of images is correct? Anyone have the same experience??

Mine dropped from 246GB in AP2 to 190GB in Ap3.... same number of images 13510..... haven't managed to complete to reprocessing of images yet.... this may change it......

Printer output incorrect/too small after upgrading to VS 2010 Crystal

I have a Windows Form application that was originally written using .net 3.5 and the version of Crystal Reports that came with Visual Studio 2008. When the VS 2010 release of Crystal Reports came out, I upgraded the application to .net 4/VS 2010 and the new Crystal release.
This application prints checks on blank check stock, so alignment of the output has to be very exact to print the checks correctly. It prints the reports using the PrintToPrinter() method of the ReportDocument class.
In the original version of the program, I had everything aligned correctly in the check report. After updating the application to the latest Crystal release,but making no changes to the report itself, I noticed that the alignment of the checks report was incorrect.
After comparing the output, I was able to determine that the new output is slightly shrunk compared to old output, almost as if it is scaling the report in some way.
I opened the report in the new report designer and verified that all page size and margin settings were correct/the same as before, and they were. The printed output is smaller than it should be based on how the report is designed. I tried adjusted the paper size, and also tried the "Dissociate Formatting Page Size and Printer Paper Size" to see if I could somehow adjust for the scaling, but nothing I tried was successful.
Our check printer is a HP LaserJet 5Si. During my investigation into the problem I discovered that if I printed the report to a pdf printer (PDFCreator) the resulting pdf did not have the same scaling/shrinking problem that I get when the report is sent directly to the LaserJet. I also printed a page from the pdf to the LaserJet using Acrobat Reader, and the output was as I expected it to be.
I only seem to be seeing the scaling/shrinking problem when I send the report directly to the LaserJet. Is there some new setting that I'm overlooking that would be applying some sort of report-wide scaling? Any other ideas as to why this is happening?

Looking for HP LaserJet 5Si at the HP website:
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?lang=en&cc=us&prodTypeId=18972&prodSeriesId=25478&taskId=135
I notice that there are several different types (hm, mx, nx, ...). Also, there are different drivers, depending on the OS.
Ensure that you are using the correct driver (hm, mx, nx, ...) for your printer and for your OS and that the driver has the latest updates from HP.
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

SAP Table index size is greater than the size of the actual table

Hello Experts,
We are resolving an issue related to database performance. The present database size is 9 Terabytes. The analysis of response times through ST03N shows that the db time is 50% of the total response time. We are planning to reorganize the most updated tables (found from DB02old tx).
Here we see that the size of the index for a table is greater than the actual size of the table. Is this possible, if yes then how can we reorganize the index as it does not allow us to reorganize the index using brspace command.
Hope to hear from you soon, and if any additional activities you can suggest to improve the performance of the database will be appreciated.
Thank you

Hi Zaheer,
online redef may help you (for a little while) , but also check WHY the index became fragmented.
Improper settings can bring the index fragmented again and you have reoccuring reorg needs.
i.e.
check if PCT_INCREASE >0 if you are using Dictionary Managed Tablespaces or locally managed tablespaces that uses a "User" allocation policy. Set it to 0 to generate uniform next extents in the online reorg.
select
            SEGMENT_NAME,
            SEGMENT_TYPE,
            round((NEXT_EXTENT*BLOCKS)/(EXTENTS*BYTES))*(BYTES/BLOCKS),
            PCT_INCREASE
        from
            DBA_SEGMENTS
        where
            OWNER='SAPR3'
        and
            SEGMENT_TYPE in ('INDEX',
                            'TABLE')
        and
            PCT_INCREASE > 0
        and segment_name in ('Yourtable','Yourindex')
In the following cases, it may be worthwhile to rebuild the index:
     --> the percentage of the space used is bad - lower than 66%: PCT_USED
     --> deleted leaf blocks represent more than 20% of total leaf blocks: DEL_LF_ROWS
     --> the height of the tree is bigger than 3: HEIGHT or BLEVEL
select
name,
'----------------------------------------------------------'    headsep,
'height               '||to_char(height,     '999,999,990')     height,
'blocks               '||to_char(blocks,     '999,999,990')     blocks,
'del_lf_rows          '||to_char(del_lf_rows,'999,999,990')     del_lf_rows,
'del_lf_rows_len      '||to_char(del_lf_rows_len,'999,999,990') del_lf_rows_len,
'distinct_keys        '||to_char(distinct_keys,'999,999,990')   distinct_keys,
'most_repeated_key    '||to_char(most_repeated_key,'999,999,990') most_repeated_key,
'btree_space          '||to_char(btree_space,'999,999,990')       btree_space,
'used_space           '||to_char(used_space,'999,999,990')        used_space,
'pct_used                     '||to_char(pct_used,'990')          pct_used,
'rows_per_key         '||to_char(rows_per_key,'999,999,990')      rows_per_key,
'blks_gets_per_access '||to_char(blks_gets_per_access,'999,999,990') blks_gets_per_access,
'lf_rows      '||to_char(lf_rows,    '999,999,990')||'        '||+
'br_rows      '||to_char(br_rows,    '999,999,990')                  br_rows,
'lf_blks      '||to_char(lf_blks,    '999,999,990')||'        '||+
'br_blks      '||to_char(br_blks,    '999,999,990')                  br_blks,
'lf_rows_len '||to_char(lf_rows_len,'999,999,990')||'        '||+
'br_rows_len '||to_char(br_rows_len,'999,999,990')                  br_rows_len,
'lf_blk_len   '||to_char(lf_blk_len, '999,999,990')||'        '||+
'br_blk_len   '||to_char(br_blk_len, '999,999,990')                br_blk_len
from
index_stats where index_name = 'yourindex'
bye
yk

Entries in table CDHDR for transaction MM02 missing after upgrade to ECC6.0

Hi,
I am supporting a client who has just performed an upgrade from 4.7 to ECC6.0 on their test system. We try and use transaction MM04 (display material master changes) or MM02 and view changes to the material master but there are no entries.
During the upgrade, the entries for transaction code MM02 in table CDHDR have been lost. Can anybody give me assistance on how to avoid this when performing the production upgrade, or even better, is there any way to get these entries back?
Thank you.
Sharon.

That shouldn't happen - entries shouldn't get lost.
Is there anything in the CDHDR table (by browsing it with SE16)? If not, then something went wrong during the upgrade....
Have there been modifications to the table? Is the the table active in SE11?
Markus

Size of domain.sites2 after upgrade to 09

hi,
I just upgraded from 08 to 09. I'm having problems uploading photo albums - the pages show up without the albums. I checked last week's domain.sites2 in time machine and it was 500.3 mb. I have only added one pic and minimal text, but domain.sites2 is now 744.1 mb. What's using all the space? Could this somehow explain my uploading problem?
thanks,
tony

Thanks, TD. Perfect.
Alexa

Index size greated then Table Size

Hi all,
We are running BI7.0 in our environment.
One of the tables' index size is much greated than the table itself. The Details are listed below:
Table Name: RSBERRORLOG
Total Table Size: 141,795,392 KB
Total Index Size: 299,300,576 KB
Index:
F5: Index Size / Allocated Size: 50%
Is there any reason that the index should grow more than Table? If so, would Reorganizing index help and if this can be controlled?
Please letme know on this as I am not very clear on DB much.
Thanks and Regards,
Raghavan

Hi Hari
Its basically degenerated index. You can follow the below steps
1. Delete some entries from RSBERRORLOG.
BI database growing at 1 Gb per day while no data update on ECC
2. Re-organize this table from BRSPACE . Now the size of the table would be very less. I do not remember if this table has a LONG RAW field ( in that case export /import) of this table would be required. ---Basis job
3. Delete and recreate Index on this table
You will gain lot of space.
I assumed you are on Oracle.
More information on reoganization is LINK: [Reorg|TABLE SPACE REORGANIZATION !! QUICK EXPERT INPUTS;
Anindya
Regards
Anindya

Lightroom export file size: why so small? How can I maximize image quality?

My image file sizes are much smaller after editing and exporting through Lightroom. Is it impossible to maintain original file size to preserve image quality? Will this smaller file size have negative impact on prints? Any help is appreciated!

Per Berntsen wrote:
My view on this is somewhat different ...
Jpgs should never be edited, except as a last resort. And it defeats the purpose of working with raw files if you export a jpg, and then edit it.
Agreed. Unfortunately there are many cameras that only output JPEG format files. The camera file (or any other original JPEG file) is your "raw" unedited file inside LR. If you need to send the file to someone else for further editing who doesn't have LR then Exporting with 100% Quality setting might make sense. I say "might" because it's still possible to get very good results using lower Quality setting JPEGs if you only re-save the file one (1) time after further editing. I agree that 16 bit, ProPhoto RGB, TIFF Export files are best for "critical" work and when using 'Edit in Photoshop' from LR.
I suggest taking a look at the JPEG compression image tests on Jeffrey Friedl's Blog. It's a wealth of information! LR's Quality settings range from 0% to 100% or 100 Quality levels. In reality there are only 13 Quality levels, which are the same as in PS.
JPEG QUALITY SETTINGS
Photoshop
Description
Lightroom
0
Low
0-7%
1
Low
8-15%
2
Low
16-23%
3
Low
24-30%
4
Low
31-38%
5
Med
39-46%
6
Med
47-53%
7
Med
54-61%
8
High
62-69%
9
High
70-76%
10
Max
77-84%
11
Max
85-92%
12
Max
93-100%
I use LR JPEG Quality settings of 77-84% for outside printing and LR 62-69% for web posting. I've yet to see any compression artifacts using these settings and I am a pixel-peeper!
Per Berntsen wrote:
If someone gives me a jpg to edit, I always save it as a tiff and convert to 16-bit, to minimize furhter deterioration. I realize that this will not be true 16-bit - no information is added to the image - but my impression is that it will withstand heavy editing better, and not end up with a comb-like histogram.
Why not simply Import the JPEG file into LR and do all your editing non-destructively? There's no need to convert the JPEG file to TIFF unless you need to use LR 'Edit in PS.' Lightroom uses a16 bit/color, ProPhoto RGB, Linear Gamma workspace for all images even when editing sRGB JPEG files.

MSSQL 2008 - Database size getting smaller after EHP upgrade??

Hi All,
Did anyone observe the DB size of MSSQL 2008 after EHP upgrade?
In my two system, after upgraded to EHP5 and EHP2 respectively, the database is getting smaller compare to before upgrade, estimated 5-10gb.
EHP upgrade is unlike DBEXPORT, it shouldn't have any reorganization features and so do MSSQL.
Any idea?
Cheers,
Nicholas Chang

> Right after upgrade is smaller and after sgen, db size is bigger than source.
So it's ok.
> As system was upgrade from ECC6 to EHP5 with Central Application, HCM and Finance .... the after upgrade size should bigger than the source even before SGEN. Your kind input is mostly welcome.
If the source system was compiled completely (using SGEN) then you need to compare the sizes of the target system also, otherwise you compare apple with pies.
Another reason may be that index compression was activated:
Note 1459005 - Enabling index compression for SQL Server
You could now upgrade to SQL Server 2008 R2 and apply
Note 1488135 - Database compression for SQL Server
this will save additional space (30 - 50 %).
Markus

Mavericks After Upgrading to 10.9.2 the font size in the address/seach bar has changed to be small.

After upgrading to Mavericks 10.9.2 the text in the address/seach bar on Safari is a lot smaller. This is not a screen resolution issue. The fonts in Finder are larger than they were before anoying fix for this would also be nice. It is also not a screen resolution issue.
I really do not know what Apple are doing with quality control with Mavericks. The 3 month GMAIL problems have not been fixed with this upgrade and you also have a lot of font size changes accross you whole machine, within mail, finder and safari.
Any help appreciated.
Mark
Message to Apple:
Mavericks reminds me of all the old problems I had with Windows before I moved to Mac. Prior to Mavericks upgrades would not change screen resolutions, Font sizes etc. The GMAIL issue has not been fixed.
It is inconceivable to me that you could release this product which does not support basic mail functionality for one of the largest email services on the internet ie. GMAIL and then take 3-4 months and still not fixed with the 10.9.2 upgrade. What are you guys doing. The loss of productivity for people is beyond comprehension.
Can we please get a fix for GMAIL in Mavericks that actually works.

avjebs wrote:
I got this e-mail from WD a few days ago:
Dear WD Registered Customer,
UPDATE: November 1st, 2013
As a valued WD customer we want to make you aware of new reports of Western Digital and other external HDD products experiencing data loss when updating to Apple's OS X Mavericks (10.9). WD is urgently investigating these reports and the possible connection to the WD Drive Manager, WD Raid Manager and WD SmartWare software applications. Until the issue is understood and the cause identified, WD strongly urges our customers to uninstall these software applications before updating to OS X Mavericks (10.9), or delay upgrading. If you have already upgraded to Mavericks, WD recommends that you remove these applications and restart your computer. If you have already upgraded to Mavericks and are experiencing difficulty in accessing your external hard drive, please do not save anything to the drive, disconnect the drive from your computer, and contact Western Digital Customer Service at http://support.wd.com/country/ for further assistance.
The WD Drive Manager, WD Raid Manager, and WD SmartWare software applications are not new and have been available from WD for many years. However, solely as a precaution WD has removed these applications from our website as we investigate this issue.
Sincerely,
Western Digital
THIS is very disturbing news from WD.

Significant slowdown of Time Machine after upgrade to Lion; indexing problem

After upgrading to Lion over the weekend I notice a significant slowdown of Time Machine processing. I assumed the first backup or two would take some time but it's been a couple of days. The process always hangs up at the "Indexing backup" stage. It takes a couple of hours to finish.
I found several threads relating to slowed down backups on Lion, most seem to hang at the "Preparing" stage (not the same symptom) but I did find some good diagnostic pointers. I installed the widget to see what kind of messages were being produced and found a few dozen "Waiting for index to be ready (100)" messages at the end of the stream. Further research - this is not a good thing :-) It seems a couple of such messages can be ok, but this many usually indicates a problem. I'm going to discount the possibility of a hardware failure because everything was perfectly fine up to the point I made the upgrade. Plus the prepare and copy seem to proceed at the expected speed (I watched the most recent cycle just to be sure).
Here is the full message log (it's still running at the moment):
Starting standard backup
Attempting to mount network destination URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
Mounted network destination at mountpoint: /Volumes/Paul DiMarzio's Time Capsul using URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Paul DiMarzio's Time Capsul/Paul DiMarzio’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
12.15 GB required (including padding), 490.69 GB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
I further found the advice and instructions on how to run the disk utility on the sparsebundle. I did a verify and repair, and the results came back that the drive appears to be ok (it did not say that it explicitly repaired anything).
But the problem remains.
I use a 1TB Time Capsule with plenty of free capacity (only half full). The TC and my MacBook are both hardwired into the home network, networking speed has never been an issue.
I'd sure hate to delete the backup file and start from scratch, there's over a year's worth of data there and I have, occassionally, wanted to go in there and pick up a downlevel or subsequently deleted file.
Any advice on other diagnostics or repair options to take? Thanks!
Paul

After posting I decided to keep trying to slog my way through the troubleshooting guide. Some of the steps are beyond my understanding but I did follow the advice in #D2 to delete the .Spotlight-V100 file from the sparsebundle. That action does seem to have done the trick, the backups are now completing in normal time. I ran a couple just to be sure. I've verified the backups with BackupLoupe and entered the Time Machine, all appears to be in order and as expected. The only odd side effect is that the backup volume is no longer ejected after completion but that might just be an artifact of all my mounting/de-mounting and playing with Finder. Anyway a very small price to pay for what looks to be a working system again.
Hopefully the good behavior will last through a few days and a few reboots :-)
ps - if you're reading this and don't know about the troublshooting guide it's here: http://web.me.com/pondini/Time_Machine/Troubleshooting.html (thanks pondini)

Java process table empty after upgrade solution manager 7.1 Sp10

Hi Experts,
I have installed solution manager 7.1 SP3 and completed the SP10 patch upgrade using SUM tool. The upgrade was completed successfully. After upgrade igswd was red. Then i copied the Igs files in kernel files. Now ABAP instance and Igs is working now but JAVA is not coming up. JAVA process table also empty. Can any one help me to solve this issue. Attached the error for reference.
trc file: "dev_disp", trc level: 1, release: "721"
sysno      00
sid        VSM
systemid   562 (PC with Windows NT)
relno      7210
patchlevel 0
patchno    201
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    \\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
pid        5448
kernel runs with dp version 138000(ext=120000) (@(#) DPLIB-INT-VERSION-138000-UC)
length of sys_adm_ext is 592 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (00 5448) [dpxxdisp.c   1316]
shared lib "dw_xml.dll" version 201 successfully loaded
shared lib "dw_xtc.dll" version 201 successfully loaded
shared lib "dw_stl.dll" version 201 successfully loaded
shared lib "dw_gui.dll" version 201 successfully loaded
shared lib "dw_mdm.dll" version 201 successfully loaded
shared lib "dw_rndrt.dll" version 201 successfully loaded
shared lib "dw_abp.dll" version 201 successfully loaded
shared lib "dw_sym.dll" version 201 successfully loaded
shared lib "dw_aci.dll" version 201 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
use internal message server connection to port 3900
rdisp/dynamic_wp_check : 1
rdisp/calculateLoadAverage : 1
Tue Apr 01 19:02:09 2014
*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6479]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
display_tcp_ip: 0
DpIPCInit2: write dp-profile-values into sys_adm_ext
DpIPCInit2: start server >VKCSOL_VSM_00                           <
DpShMCreate: sizeof(wp_adm) 42864 (2256)
DpShMCreate: sizeof(tm_adm) 5517056 (27448)
DpShMCreate: sizeof(wp_ca_adm) 64000 (64)
DpShMCreate: sizeof(appc_ca_adm) 64000 (64)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080
DpShMCreate: sizeof(comm_adm) 1384080 (2744)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (296)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (80)
DpShMCreate: sizeof(vmc_adm) 0 (2160)
DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: sizeof(j2ee_adm) 3952
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DDE0050, size: 7174832)
DpShMCreate: allocated sys_adm at 000000000DDE0060
DpShMCreate: allocated wp_adm_list at 000000000DDE30B0
DpShMCreate: allocated wp_adm at 000000000DDE32A0
DpShMCreate: allocated tm_adm_list at 000000000DDEDA20
DpShMCreate: allocated tm_adm at 000000000DDEDA70
DpShMCreate: allocated wp_ca_adm at 000000000E330980
DpShMCreate: allocated appc_ca_adm at 000000000E340390
DpShMCreate: allocated comm_adm at 000000000E34FDA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 000000000E4A1C40
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated gw_adm at 000000000E4A1CF0
DpShMCreate: allocated j2ee_adm at 000000000E4A1D30
DpShMCreate: allocated ca_info at 000000000E4A2CB0
DpShMCreate: allocated wall_adm at 000000000E4A2D40
DpCommAttachTable: attached comm table (header=000000000E34FDA0/ft=000000000E34FDB0)
DpSysAdmIntInit: initialize sys_adm
rdisp/test_roll : roll strategy is DP_NORMAL_ROLL
dia token check not active (10 token)
MBUF state OFF
DpCommInitTable: init table for 500 entries
DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm
rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> EsILock: use spinlock for locking
<ES> InitFreeList
<ES> block size is 4096 kByte.
<ES> Info: em/initial_size_MB( 16383MB) not multiple of em/blocksize_KB( 4096KB)
<ES> Info: em/initial_size_MB rounded up to 16384MB
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 4095 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 192 MB
mm.dump: set global maximum dump mem to 192 MB
EsRegisterEmCheck: Register EmGetEsHandles at 000000013FC48640
DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
MPI: dynamic quotas disabled.
MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
J2EE server info
start = TRUE
state = STARTED
pid = 5824
argv[0] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
argv[1] = D:\usr\sap\VSM\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=65000
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=VSM
argv[7] = -DSAPMYNAME=VKCSOL_VSM_00
argv[8] = -DSAPPROFILE=\\VKCSOL\sapmnt\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 4.0.1 4.0.1 5.1) [dpxxdisp.c   1702]
***LOG Q0K=> DpMsAttach, mscon ( VKCSOL) [dpxxdisp.c   12707]
MBUF state LOADING
DpStartStopMsg: send start message (myname is >VKCSOL_VSM_00                           <)
DpStartStopMsg: start msg sent
CCMS: Initialized monitoring segment of size 60000000.
CCMS: Initialized CCMS Headers in the shared monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: AlMsUpload called by wp 1024.
Tue Apr 01 19:02:10 2014
01.04.2014 13:32:10.628 PID=5448, TID=5744 SapTimer info. QPC/Windows time mismatch. System suspended, busy, missing ticks. Mismatch QpcTime-WindowsTime: -168 millisec (max +0). Slept 1000 millisec, Qpc elapsed: +1000 millisec, WindowsUtc elapsed +1168 millisec. SapTime-WindowsUtcTime=-1 seconds. TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-1028 millisec (*).
Tue Apr 01 19:02:11 2014
CCMS: AlMsUpload successful for D:\usr\sap\VSM\DVEBMGS00\log\ALMTTREE.DAT (2189 MTEs).
Tue Apr 01 19:02:13 2014
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1296]
MBUF state ACTIVE
DpWpBlksLow: max wp blocks in queue is 800 (80 %)
MBUF component UP
DpMsgProcess: 1 server in MBUF
DpAppcBlksLow: max appc blocks in queue is 500 (50 %)
Tue Apr 01 19:02:21 2014
DpModState: change server state from STARTING to ACTIVE
Tue Apr 01 19:02:23 2014
***LOG Q0I=> NiIRead: P=127.0.0.1:61107; L=127.0.0.1:65000: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5086]
*** ERROR => NiIRead: SiRecv failed for hdl 33/sock 1008
    (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:61107; L=127.0.0.1:65000) [nixxi.cpp    5086]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5824)
*** ERROR => DpProcKill: kill failed [dpntdisp.c   397]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Regards
Jose H.

Hi Ashutosh,
Thanks for your immediate reply. Please find the log below.
trc file: "dev_server0", trc level: 1, release: "721"
node name   : ID3506750
pid         : 8068
system name : VSM
system nr. : 00
started at : Sat Mar 29 13:41:08 2014
arguments :
   arg[00] : D:\usr\sap\VSM\DVEBMGS00\exe\jlaunch.exe
   arg[01] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
   arg[02] : -DSAPINFO=VSM_00_server
   arg[03] : pf=D:\usr\sap\VSM\SYS\profile\VSM_DVEBMGS00_VKCSOL
   arg[04] : -DSAPSTART=1
Used property files
-> files [00] : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID3506700 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID3506750 : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
Worker nodes
-> [00] ID3506700            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID3506750            : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host    : VKCSOL
-> ms port    : 3901
-> OS libs    : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
-> Admin URL :
-> run mode   : safe
-> run action : UPGRADE
-> enabled    : yes
[Thr 19300] Sat Mar 29 13:41:08 2014
[Thr 19300] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 19300] JLaunchRequestQueueInit: create pipe listener thread
[Thr 19300] JLaunchInitSignalHandling: signal handling is disabled
[Thr 4928] WaitSyncSemThread: Thread 4928 started as semaphore monitor thread.
[Thr 23444] JLaunchRequestFunc: Thread 23444 started as listener thread for np messages.
[Thr 19300] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
[Thr 19300] MPI: dynamic quotas disabled.
[Thr 19300] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
[Thr 19300] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 19300] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 19300] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 19300] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 19300] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048m [jstartxx.c   2800]
[Thr 19300] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
JStartupIReadSection: read node properties [ID3506750]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4
-> java parameters    : -XX:MaxNewSize=600M -XX:NewSize=600M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:TargetSurvivorRatio=90 -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -verbose:gc -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HeapDumpPath=OOM.hprof -XX:+HeapDumpOnOutOfMemoryError -Djco.jarm=1 -Djava.awt.headless=true -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dsun.io.useCanonCaches=false -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Dcom.sap.jvm.scenario=j2ee -XX:+JavaMonitorsInStackTrace -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0 -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
-> java vm version    : 4.1.024 1.6-b04
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 2048M
-> init heap size     : 2048M
-> stack size         : 2M
-> root path          : D:\usr\sap\VSM\DVEBMGS00\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar
-> shutdown class     : com.sap.engine.boot.Start
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 50021
-> shutdown timeout   : 120 sec.
[Thr 19300] JLaunchISetDebugMode: set debug mode [no]
[Thr 9092] JLaunchIStartFunc: Thread 9092 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack   : 2097152 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -XX:MaxNewSize=600M
-> arg[ 4]: -XX:NewSize=600M
-> arg[ 5]: -XX:MaxPermSize=512M
-> arg[ 6]: -XX:PermSize=512M
-> arg[ 7]: -XX:+UseConcMarkSweepGC
-> arg[ 8]: -XX:+DisableExplicitGC
-> arg[ 9]: -XX:TargetSurvivorRatio=90
-> arg[ 10]: -XX:SurvivorRatio=4
-> arg[ 11]: -XX:+PrintGCDetails
-> arg[ 12]: -XX:+PrintGCTimeStamps
-> arg[ 13]: -verbose:gc
-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 15]: -XX:HeapDumpPath=OOM.hprof
-> arg[ 16]: -XX:+HeapDumpOnOutOfMemoryError
-> arg[ 17]: -Djco.jarm=1
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Djava.security.policy=./java.policy
-> arg[ 20]: -Djava.security.egd=file:/dev/urandom
-> arg[ 21]: -Dsun.io.useCanonCaches=false
-> arg[ 22]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 23]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 24]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 25]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 26]: -Dcom.sap.jvm.scenario=j2ee
-> arg[ 27]: -XX:+JavaMonitorsInStackTrace
-> arg[ 28]: -Xbootclasspath/p:D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/Agent.jar
-> arg[ 29]: -Dcom.wily.introscope.agent.agentName=VSM_DVEBMGS00_server0
-> arg[ 30]: -Dcom.wily.introscope.agentProfile=D:/usr/sap/DAA/SMDA97/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-09-13/wily/IntroscopeAgent.profile
-> arg[ 31]: -Dstartup.mode=SAFE
-> arg[ 32]: -Dstartup.action=UPGRADE
-> arg[ 33]: -Dsys.global.dir=D:\usr\sap\VSM\SYS\global
-> arg[ 34]: -Dapplication.home=D:\usr\sap\VSM\DVEBMGS00\exe
-> arg[ 35]: -Djava.class.path=D:\usr\sap\VSM\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\VSM\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 36]: -Djava.library.path=D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\VSM\DVEBMGS00\j2ee\os_libs;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\VSM\DVEBMGS00\exe;D:\usr\sap\VSM\SYS\exe\uc\NTAMD64
-> arg[ 37]: -Dmemory.manager=2048M
-> arg[ 38]: -Xmx2048M
-> arg[ 39]: -Xms2048M
-> arg[ 40]: -Xss2M
-> arg[ 41]: -DLoadBalanceRestricted=no
-> arg[ 42]: -Djstartup.mode=JCONTROL
-> arg[ 43]: -Djstartup.ownProcessId=8068
-> arg[ 44]: -Djstartup.ownHardwareId=I0649086862
-> arg[ 45]: -Djstartup.whoami=server
-> arg[ 46]: -Djstartup.debuggable=no
-> arg[ 47]: -Xjvmx
-> arg[ 48]: -XsapSystem=00
-> arg[ 49]: -XmonGcCallback
-> arg[ 50]: -DSAPINFO=VSM_00_server
-> arg[ 51]: -DSAPSTART=1
-> arg[ 52]: -DSAPSTARTUP=1
-> arg[ 53]: -DSAPSYSTEM=00
-> arg[ 54]: -DSAPSYSTEMNAME=VSM
-> arg[ 55]: -DSAPMYNAME=VKCSOL_VSM_00
-> arg[ 56]: -DSAPDBHOST=VKCSOL
-> arg[ 57]: -Dj2ee.dbhost=VKCSOL
(CompilerOracle read from file D:\usr\sap\VSM\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
[Thr 9092] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [server0]
[Thr 20084] Sat Mar 29 13:41:10 2014
[Thr 20084] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
2.781: [GC 2.781: [ParNew: 409600K->2306K(512000K), 0.0126041 secs] 409600K->2306K(1994752K), 0.0127881 secs] [Times: user=0.05 sys=0.00, real=0.01 secs]
[Thr 20084] Sat Mar 29 13:41:11 2014
[Thr 20084] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.JStartupFramework
[Thr 20084] JLaunchISetClusterId: set cluster id 3506750
[Thr 20084] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 20084] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
Sat Mar 29 13:41:23 2014
15.071: [GC 15.071: [ParNew: 411906K->16315K(512000K), 0.0306641 secs] 411906K->16315K(1994752K), 0.0309011 secs] [Times: user=0.13 sys=0.00, real=0.03 secs]
Sat Mar 29 13:41:32 2014
24.118: [GC 24.118: [ParNew: 425915K->29114K(512000K), 0.0363407 secs] 425915K->29114K(1994752K), 0.0365634 secs] [Times: user=0.11 sys=0.02, real=0.04 secs]
[Thr 18736] Sat Mar 29 13:41:38 2014
[Thr 18736] JHVM_RegisterNatives: com.sap.mona.api.JMonAPI
[Thr 18736] CCMS: openMonitoringSegment(): inside static JMON Lib: already connected.
[Thr 17644] JHVM_RegisterNatives: com.sap.mw.rfc.driver.CpicDriver
[Thr 19340] JHVM_RegisterNatives: com.sap.security.core.server.vsi.service.jni.VirusScanInterface
[Thr 7816] Sat Mar 29 13:41:39 2014
[Thr 7816] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7816] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 25/sock 7884
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17936] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 7888
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
31.816: [GC 31.816: [ParNew[Thr 21936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 7856
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 2800] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 2800] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 9/sock 7860
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
: 438714K->67978K(512000K), 0.0626636 secs] 438714K->67978K(1994752K), 0.0628963 secs] [Times: user=0.11 sys=0.08, real=0.06 secs]
[Thr 7276] Sat Mar 29 13:41:40 2014
[Thr 7276] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7988
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 24572] Sat Mar 29 13:41:42 2014
[Thr 24572] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24572] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 8132
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 5092] Sat Mar 29 13:41:43 2014
[Thr 5092] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5092] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 8088
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 20084] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
[Thr 24276] Sat Mar 29 13:41:44 2014
[Thr 24276] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24276] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 8480
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 1316] Sat Mar 29 13:41:45 2014
[Thr 1316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 1316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 9292
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 13068] Sat Mar 29 13:41:46 2014
[Thr 13068] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13068] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 9736
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 19652] JLaunchISetState: change state from [Starting applications (10)] to [Running (3)]
[Thr 17680] Sat Mar 29 13:41:47 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 9736
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 23760] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 23760] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 10/sock 5976
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:41:48 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 9736
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:41:49 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 9736
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:41:50 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6272
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 5348] Sat Mar 29 13:41:51 2014
[Thr 5348] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5348] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6336
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17548] Sat Mar 29 13:41:52 2014
[Thr 17548] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17548] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6548
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 4216] Sat Mar 29 13:41:53 2014
[Thr 4216] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 4216] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6424
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 23788] Sat Mar 29 13:41:54 2014
[Thr 23788] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 23788] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6844
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6100] Sat Mar 29 13:41:55 2014
[Thr 6100] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6100] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7448
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6828] Sat Mar 29 13:41:56 2014
[Thr 6828] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6828] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6216
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 644] Sat Mar 29 13:41:57 2014
[Thr 644] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 644] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 5992
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 7376] Sat Mar 29 13:41:58 2014
[Thr 7376] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7376] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6136
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 24096] Sat Mar 29 13:41:59 2014
[Thr 24096] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24096] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6004
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 24460] Sat Mar 29 13:42:00 2014
[Thr 24460] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24460] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6276
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 13452] Sat Mar 29 13:42:01 2014
[Thr 13452] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13452] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7328
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17884] Sat Mar 29 13:42:03 2014
[Thr 17884] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17884] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 7372
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6616] Sat Mar 29 13:42:04 2014
[Thr 6616] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6616] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7200
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 3136] Sat Mar 29 13:42:05 2014
[Thr 3136] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 3136] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6344
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 8284] Sat Mar 29 13:42:06 2014
[Thr 8284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 8284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 7380
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 19240] Sat Mar 29 13:42:07 2014
[Thr 19240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6940
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 21316] Sat Mar 29 13:42:08 2014
[Thr 21316] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21316] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 5988
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 22436] Sat Mar 29 13:42:09 2014
[Thr 22436] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 22436] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 7368
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 20936] Sat Mar 29 13:42:10 2014
[Thr 20936] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 20936] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 7528
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 18784] Sat Mar 29 13:42:11 2014
[Thr 18784] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 18784] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 4460
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 21320] Sat Mar 29 13:42:12 2014
[Thr 21320] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 21320] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6148
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 19632] Sat Mar 29 13:42:13 2014
[Thr 19632] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19632] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 5948
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 8684] Sat Mar 29 13:42:14 2014
[Thr 8684] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 8684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6012
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 7468] Sat Mar 29 13:42:15 2014
[Thr 7468] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7468] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6032
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 5588] Sat Mar 29 13:42:16 2014
[Thr 5588] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5588] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 1032
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 2036] Sat Mar 29 13:42:17 2014
[Thr 2036] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 2036] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6052
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 6692] Sat Mar 29 13:42:18 2014
[Thr 6692] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6692] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6188
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 5184] Sat Mar 29 13:42:19 2014
[Thr 5184] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5184] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6192
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 5604] Sat Mar 29 13:42:20 2014
[Thr 5604] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5604] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6220
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 15996] Sat Mar 29 13:42:21 2014
[Thr 15996] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 15996] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6236
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:22 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6236
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:23 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6236
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:24 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6236
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:26 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6064
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 19856] Sat Mar 29 13:42:27 2014
[Thr 19856] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19856] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6184
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 24128] Sat Mar 29 13:42:28 2014
[Thr 24128] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24128] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6248
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 13684] Sat Mar 29 13:42:29 2014
[Thr 13684] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 13684] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6260
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 7384] Sat Mar 29 13:42:30 2014
[Thr 7384] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7384] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6264
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 7432] Sat Mar 29 13:42:31 2014
[Thr 7432] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7432] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6292
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6700] Sat Mar 29 13:42:32 2014
[Thr 6700] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6700] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6304
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 7272] Sat Mar 29 13:42:33 2014
[Thr 7272] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7272] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6340
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 19864] Sat Mar 29 13:42:34 2014
[Thr 19864] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 19864] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6392
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 5608] Sat Mar 29 13:42:35 2014
[Thr 5608] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 5608] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6404
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 7160] Sat Mar 29 13:42:36 2014
[Thr 7160] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7160] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6416
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 14536] Sat Mar 29 13:42:37 2014
[Thr 14536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 14536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 7340
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 24404] Sat Mar 29 13:42:38 2014
[Thr 24404] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24404] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6232
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 22756] Sat Mar 29 13:42:39 2014
[Thr 22756] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 22756] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6076
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6284] Sat Mar 29 13:42:40 2014
[Thr 6284] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6284] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 7472
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 12696] Sat Mar 29 13:42:41 2014
[Thr 12696] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 12696] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 35/sock 6380
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 24180] Sat Mar 29 13:42:42 2014
[Thr 24180] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 24180] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 36/sock 6420
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 23444] Sat Mar 29 13:42:43 2014
[Thr 23444] JLaunchRequestFunc: receive command:17, argument:0 from pid:20668
[Thr 23444] JLaunchIShutdownInvoke: set shutdown interval (stop:1396080763/end:1396080883/TO:120)
[Thr 23444] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 23444] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 8780] JLaunchISetState: change state from [Running (3)] to [Waiting for stop (4)]
[Thr 8780] JLaunchISetState: change state from [Waiting for stop (4)] to [Stopping (5)]
[Thr 5188] JHVM_RegisterNatives: com.sap.bc.proj.jstartup.sadm.ShmCache
[Thr 7240] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 7240] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 37/sock 6376
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 6536] Sat Mar 29 13:42:44 2014
[Thr 6536] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 6536] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 38/sock 6852
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 18244] Sat Mar 29 13:42:46 2014
[Thr 18244] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 18244] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 39/sock 6348
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:47 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 32/sock 6348
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
[Thr 17680] Sat Mar 29 13:42:48 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 127.0.0.1:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 33/sock 6348
    (SI_ECONN_REFUSE/10061; I4; ST; 127.0.0.1:3300) [nixxi.cpp    3285]
[Thr 22796] CCMS: closeMonitoringSegment(): inside static JMON Lib: nothing to do.
[Thr 8780] JLaunchISetState: change state from [Stopping (5)] to [Stopped (6)]
[Thr 17680] Sat Mar 29 13:42:49 2014
[Thr 17680] ***LOG Q0I=> NiPConnect2: 192.168.10.62:3300: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3285]
[Thr 17680] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 34/sock 6348
    (SI_ECONN_REFUSE/10061; I4; ST; 192.168.10.62:3300) [nixxi.cpp    3285]
Heap
par new generation   reserved 614400K, committed 614400K, used 313963K [0x000000007fff0000, 0x00000000a57f0000, 0x00000000a57f0000)
eden space 409600K, 60% used [0x000000007fff0000, 0x000000008f028658, 0x0000000098ff0000)
from space 102400K, 66% used [0x0000000098ff0000, 0x000000009d2528e8, 0x000000009f3f0000)
to   space 102400K,   0% used [0x000000009f3f0000, 0x000000009f3f0000, 0x00000000a57f0000)
concurrent mark-sweep generation reserved 1482752K, committed 1482752K, used 0K [0x00000000a57f0000, 0x00000000ffff0000, 0x00000000ffff0000)
concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 70349K [0x00000000ffff0000, 0x000000011fff0000, 0x000000011fff0000)
[Thr 18896] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 18896] JLaunchCloseProgram: good bye (exitcode = 0)
Regards
Jose H.

Index size keep growing while table size unchanged

Hi Guys,
I've got some simple and standard b-tree indexes that keep on acquiring new extents (e.g. 4MB per week) while the base table size kept unchanged for years.
The base tables are some working tables with DML operation and nearly same number of records daily.
I've analysed the schema in the test environment.
Those indexes do not fulfil the criteria for rebuild as follows,
- deleted entries represent 20% or more of the current entries
- the index depth is more then 4 levels
May I know what cause the index size keep growing and will the size of the index reduced after rebuild?
Grateful if someone can give me some advice.
Thanks a lot.
Best regards,
Timmy

Please read the documentation. COALESCE is available in 9.2.
Here is a demo for coalesce in 10G.
YAS@10G>truncate table t;
Table truncated.
YAS@10G>select segment_name,bytes from user_segments where segment_name in ('T','TIND');
SEGMENT_NAME              BYTES
T                         65536
TIND                      65536
YAS@10G>insert into t select level from dual connect by level<=10000;
10000 rows created.
YAS@10G>commit;
Commit complete.
YAS@10G>
YAS@10G>select segment_name,bytes from user_segments where segment_name in ('T','TIND');
SEGMENT_NAME              BYTES
T                        196608
TIND                     196608We have 10,000 rows now. Let's delete half of them and insert another 5,000 rows with higher keys.
YAS@10G>delete from t where mod(id,2)=0;
5000 rows deleted.
YAS@10G>commit;
Commit complete.
YAS@10G>insert into t select level+10000 from dual connect by level<=5000;
5000 rows created.
YAS@10G>commit;
Commit complete.
YAS@10G>select segment_name,bytes from user_segments where segment_name in ('T','TIND');
SEGMENT_NAME              BYTES
T                        196608
TIND                     327680Table size is the same but the index size got bigger.
YAS@10G>exec show_space('TIND',user,'INDEX');
Unformatted Blocks .....................               0
FS1 Blocks (0-25) .....................               0
FS2 Blocks (25-50) .....................               6
FS3 Blocks (50-75) .....................               0
FS4 Blocks (75-100).....................               0
Full Blocks        .....................              29
Total Blocks............................              40
Total Bytes.............................         327,680
Total MBytes............................               0
Unused Blocks...........................               0
Unused Bytes............................               0
Last Used Ext FileId....................               4
Last Used Ext BlockId...................          37,001
Last Used Block.........................               8
PL/SQL procedure successfully completed.We have 29 full blocks. Let's coalesce.
YAS@10G>alter index tind coalesce;
Index altered.
YAS@10G>select segment_name,bytes from user_segments where segment_name in ('T','TIND');
SEGMENT_NAME              BYTES
T                        196608
TIND                     327680
YAS@10G>exec show_space('TIND',user,'INDEX');
Unformatted Blocks .....................               0
FS1 Blocks (0-25) .....................               0
FS2 Blocks (25-50) .....................              13
FS3 Blocks (50-75) .....................               0
FS4 Blocks (75-100).....................               0
Full Blocks        .....................              22
Total Blocks............................              40
Total Bytes.............................         327,680
Total MBytes............................               0
Unused Blocks...........................               0
Unused Bytes............................               0
Last Used Ext FileId....................               4
Last Used Ext BlockId...................          37,001
Last Used Block.........................               8
PL/SQL procedure successfully completed.The index size is still the same but now we have 22 full and 13 empty blocks.
Insert another 5000 rows with higher key values.
YAS@10G>insert into t select level+15000 from dual connect by level<=5000;
5000 rows created.
YAS@10G>commit;
Commit complete.
YAS@10G>select segment_name,bytes from user_segments where segment_name in ('T','TIND');
SEGMENT_NAME              BYTES
T                        262144
TIND                     327680Now the index did not get bigger because it could use the free blocks for the new rows.

Table index size in DB02 smaller after upgrade

Similar Messages

Maybe you are looking for