Shadow migration
FishWorks Q3 release comes with Shadow Migration which looks like a fantastic feature!
But where is it in the BUI? I can see the place to configure the source when creating a share but after that there is nothing, yet the documentation talks about viewing the progress and being able to cancel migrations. I can't find these features in the BUI, where are they?
I can see in the CLI that a migration has many thousands of errors. What are the errors? Why are they not reported?
Why can't I use shadow migration to migrate from a linux NFS server? It doesn't work unless you set NFS_CLIENT_VERSMAX=3 (instead of 4) which of course is not a supported change and reduces the functionality of migrations from solaris servers.
Talking of migrations from solaris servers, it doesn't work. I've tried to use it but it transfers a small amount of files, gives many tens of thousands of errors, and then hangs. It's impossible to see what the errors are and why it is hanging.
Is anyone able to assist or provide ideas about these issues?
Did you install the latest software, released a few days ago?
It adresses several issues regarding shadow migration.
Similar Messages
-
Backing up database with read-only tablespaces
I am trying to develop a script that will dynamically build RMAN scripts for backing up
a database with read-only tablespaces. The application running on this database creates
new tablespaces in read-write mode on weekly basis, populates them, and then puts them in read-only mode. So I need to backup all read-write tablespaces plus take backup of all read-only tablespaces once. The problem is that the application also includes a process that puts a tablespace back into read-write mode, updates it, and puts it back into read-write mode. So I need to be able to access "a history" of the tablespace - when was it put into read-only mode - to compare it with a history of backups. While history of backups is available in RMAN views, I couldn't find any way to extract tablspaces
history.
There should be RMAN command to the effect
"backup all read-write tablespaces and read-only tablespaces if they have not been backed up at least once since becoming read-only".
Regards,
Sev
nulljust rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off. -
Hi all,
This question is specific to the scenario of a cutover in a IS-utility (fall back strategy). The scenario is: consider a utility compnay going live on ISU. The SAP ERP was already running in the company. The thing is when the company starts to bring ISU to go live they want to run ERP integrated with ISU in the same server machine.Thus they have to close ERP system for the period when ISU is going live. The time when they go live after migration some un-forseen circumstances make the ISU cutover go bad. Thus they have to close ISU for now and rewoke ERP again until they figure out a way out of the problem.
My question is when we are migarting using emigall/ISMW we are running the objects in create mode. If the cutover went bad and the only change to the ERP is the migrated objects of ISU, in order to reverse the migrated data can we run the objects of the same migration file under delete mode. Will this make the ERP go back to what it was before migration?
waiting for your answersHello Hashmi,
Srini said: I suggest you create a parallel production environment as a copy of the current ECC at a certain point in time. After you do all your migration, apply the deltas to the new production box and then switch the production environment to the new box, if everything goes well. The advantage will be that you don't have to bring down your production server for a long time except for the copying and switchover. Another advantage will be that if your migration doesn't go well, you can trash the new environment and start all over depending on how bad your migration went.
In brief, I tend to disagree to having the production system in production with write/change access while doing data migration into a shadow (migration) system since (allmost) all changes done in production must be applied manually in the migration system. The question is if this is possible at all. In contrary, it won't be possible to apply changes of the shadow system (as a result of data migration) to the production system. In addition, don't forget, that copying in Srini's sense is not exactly copying data.
One last point: many basis teams are afraid of restoring the production system hence trying to defeat such an idea. Why? Well, because the have never tried this before. But wouldn't a restore a good fallback strategy?
Cheers,
Fritz -
I want to use facebook and whatsapp on torch 2 .. is there any exclusive plan to get the job done ..
9810
just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off. -
I have 5 history databases that total about 2.2 Terabytes. They use about 15 filesystems, but I can start with 2 that are isolated to only one database. I have asked for ZFS compression to be set on the filesystems, but since these are read-only tablespaces, I do not think any compression will happen. Can I simply offline, copy and rename the files from one filesystem to the other to make the compression happen?
just rsync the files to a compressed Zpool. do this using shadow migration, and you only loose access to the data for a few seconds.
1) make new dataset with compression
2) enable shadow migration between the new and old
3) change the database to use the new location
4) watch as data is automatically copied and compressed :-)
the the down side, you need extra space to pull the off. -
Migrating /etc/shadow from *nix to OS X?
Is it possible to migrate users from Linux/Unix to OS X? I really just need some way to merge a traditional /etc/shadow file with /var/db/shadow Since both are hashed via separate ways, I'm sure there's no "just copy it here".
I've seen a few re-written userlands on sourceforge that would enable the normal use of /etc/shadow on OS X, this can't be the only solution...
Thanks for reading or responding!There isn't any method I'm aware of.
The problem is that the passwords are not stored in these files - they only store a hashed/encrypted version of the password. When a user logs in, their password is encrypted using the same algorithm and then compared to the shadow file. If the encrypted versions match then the authentication succeeds.
In this way the shadow file doesn't need to store the actual password, which enhances security, but it also makes it impossible to migrate the passwords to a different system since you cannot retrieve the original password from the shadow file.
As a result I don't think there's any way to migrate passwords via this file. If you're migrating your users to a new directory server then you probably have to give them new passwords. -
Pre-Version 10 Shadow Files migration
Hi all,
Anyone know whether its possible to use the shadow file encrypted passwords from and Version 9 and 6 system, and import into the Solaris 10 Environment ??
Have a requirement to migrate 300 users from a version 6 system and 150 users from an version 9 system. And dont want to have to manually create all the user accounts and passwords from scratch.
I have previously copied the passwd and shadow contents onto other systems to speed it up. But am concerned version 10 may be using a different encryption method on the password hashing.
Any feedback would be appreciated, thanks.Check:
/etc/security/policy.conf CRYPT_DEFAULT does not need to be the same (you can import a crypt shadow file on a system configured for md5, it will simply use md5 on next password change) but CRYPT_ALGORITHMS_ALLOW must include the algorithms used on source machine. (you cannot import md5 passwords into a machine not allowing them).
Otherwise, I don't see any other possible source of trouble. -
Migrating Linux shadow-file MD5 passwords to Sun DSEE for Solaris/SunMail
Hello all,
We are about to undertake migration of an outdated mail server based on RedHat 7.2 and Sendmail/ipop3d to Sun Messaging Server (JCS6u2). While the filesystem/mail are not a problem, we're stuck at the question of how to best migrate old users' identities.
The old Linux system used user names and password hashes stored in /etc/passwd and /etc/shadow files. Hashes are mostly MD5 and a few seem like crypt.
Question is: are there known incompatibilities between password hashes (algorithms, expected format) in Linux and Sun products - Solaris/DSEE/SunMail?
That is, if we just take strings like these:
usemd5:$1$Wu7IqFT5$TeUht3OMdeSSBB3Vab4dB.:11262:0:::::134540116
usecrypt:DD2kEwCD8nies:10220::::::
Can we simply place the second column as the userPassword attribute in Sun DSEE and expect that users would be able to log in to LDAP-enabled Solaris and Sun Mail with their old passwords knownst only to them?
If not, is there some simple modification/translation of such hashes to a format accepted by Sun products?
Or are these formats/algorithms known to be incompatible somehow in a fatal manner, so our only option would be generation of new passwords for Sun DSEE and its clients?
Thanks,
//JimJust to reclarify or throw more information:
a password - cleartext value - testuser1 has 32-digit HEX value as - 41da76f0fc3ec62a6939e634bfb6a342
Same password when converted to Base64 pattern becomes - Qdp28Pw+xippOeY0v7ajQg==
But when I use pwdhash utility in DSE after configuring CRYPT to use MD5 hashes it becomes -
{crypt}$md5$$LiB/H70zXr3xfQPoXVuUQ1
I used below command :
pwdhash -D /opt/SUNWdsee/dsee6/ds6/slapd-oha-dev -s CRYPT testuser1
Actual hash value of pwdhash is -LiB/H70zXr3xfQPoXVuUQ1 with rest of the prefix is to meet RFC standard and salt and algo name separator.
I am wondering if Sun MD5 default uses any salt even when I haven't used or DS does it. Or if any other MD5 option is there which can be used.
Thanks,
Gaurav -
Migration form /etc/passwd and /etc/shadow to iPlanet Directory !
Hi,
we try to migrate from files (shadow passwd on Solaris) to LDAP- Server from iPlanet. So far so good. Our problem is now to migrate users, which have no password (NP in shadow) or users with an locked account (*LK* in shadow). Is there an attribute or flag, e.g. in the class shadowaccout which describes this issue.Hi Alois,
I assume that your question is about preventing locked or no-password users from logging into the directory.
The easiest would be to inactivate both no-password and locked users. I would
1) create one role for both no-password and locked users, then
2) assign the corresponding role to each user who is either locked or has no password
3) inactivate both roles.
By inactivating a role, all users possessing that particular role become inactivated. Inactivated users can not login to the directory.
I would recommend you to read the 'Advanced Entry Management' chapter of the administrator's guide.
I hope this helps.
Bertold -
Hi,
we have to migrate a server with shadow volumes to new hardware.
Assuming the following situation:
Source Server:
- SLES11 SP1 OES11
Pool DATA 500 GB with Volume DATA 500 GB almost full (Primary Volume)
Pool SH_DATA 500 GB with Volume SH_DATA 500 GB almost full (Shadow Volume)
No more space left on the Server
Target Server:
- SLES11 SP3 OES11 SP2
app. 2 TB free Space
What I found in the documentation:
Migrating with the Shadow Volume Relationship: Only 1 GB of data from the source server can be migrated to the primary volume Vol4 of the target server. If you need the data on all the volumes of source server to be migrated to the target server, perform the following:
NOTE:You require to stop the DST policies temporarily before performing migration.
1.Stop the existing DST policies.
2.Create a project to migrate the data less than or equal to 1 GB from the source server to the target server.
3.Perform the migration.
4.(Conditional) If some files or folders were open on the source server and did not get migrated to the target server, perform synchronization.
Synchronization must be performed before performing the next step.
5.Configure a DST policy on the target server to move the migrated data from the primary volume to the secondary volume.
As a result, there is space available on the primary volume of the target server to migrate additional data from the source server.
6.Stop the DST policy after the required data is moved from the primary volume Vol4 to the secondary volume Vol5.
7.Repeat Step 2 to Step 6 until the entire data is migrated.
Following the doku I have to perform 1000 migations for 1TB data?
Is there a smoother way to do the migration of the volumes?
Best regards
NicoOriginally Posted by ndecken
Hi Kevin,
sorry, I didn't saw that you was writing another post.
We didn't performed the migration yet, a step-by-step would be nice, I'll PM you my email address.
But an other scenario ;-)
One of our customers has a FC-SAN and has several LUN's on it. some of these are DST volumes.
Now he get's an iSCSI low performance storage and want to move the DST volumes off from the FC-SAN to the iSCSI storage.
Both storages are visible by the Vsphere hosts, where the fileservers reside on.
My plan is:
1. create new volume on the iSCSI storage and name it DST_VOL2
2. turn off any DST policies
3. migrate the old DST Volume named DST_VOL1 to DST_VOL2
4. dismount and delete DST_VOL1
5. rename DST_VOL2 to DST_VOL1
will this work, or is there an other possibility to do this work?
Best regards
Nico
This may be changing since I was intending to refer to this when I said Pool Move:
https://www.novell.com/documentation...move_pool.html
So hopefully the link Hans posted is only for DFS moves (which I'm not referring to).
IF the same rules apply then:
Well since we have some product limitations with the pool move at this point, I'm going to assume you're in a non-clustered setup?
If so, then I guess the only ways I can think of:
1) If you're on OES11, I believe the max size for pools in 9 TB now? Maybe you can expand the Primary pool to be large enough to then re-shift the Shadow pool back and THEN pool move and then re-shadow it? Depending upon your VMware version, you may need to use RAW disks (I think in 5.5 you're still limited to 2 TB disks?)
2) If you're going to use your above method, I think you'll need some significant downtime (I'm assuming you're using the same server, just diff. disks), because you'll need to break the DST shadow relationship, (not just stop the policies, literally de-shadow the volumes) which means users won't have access to their shadowed data and then do the copy/migrate as you mentioned.
3) IF you were going to another/different server, then you could use the miggui with my unsupported method (or maybe it's supported now) which only involves a brief break of the shadow (just long enough to build the migration project so it sees 2 diff. volumes) and then away you go.
Unless someone has another/better way to move storage items and retain the shadow relationship? I'm not a VMware expert, but MAYBE (not sure) there's an option in VMware to migrate a vdisk from one to another (or the vmdk files??) while the system is online? But I don't think so. I know there's a storage migration, but usually that's the entire VM Guest itself, not just a specific disk.
But, IF Vmware has something nifty, you could have a VM Storage that's on the iSCSI and maybe "move" the Virtual disk to that new iSCSI storage, but again, not sure how that'd be handled or what would happen in the underlying OS. I suppose it's possible to have the VM LUN/Storage be on iSCSI, yet be presented to the Guest as regular SCSI storage since it's virtualized??
I know Massimo does lots with iSCSI and such. -
Urgent: cannot start the shadow instance at phase STARTSAP_TRANS
We are upgrading to NW2004s (ABAP only) from 640.
<u><b>How to re-start the shadow instance?</b></u>
At this point, <b>anyway we cannot start the shadow instance.</b>
At SAPMMC, the disp+work
1) first show "running but the dialog queue standstill"
2) then show" running but not connected to the message server"
3) then the disp+work dies.
Above happens in 1 minute after re-start.
<b>The dev_ms reads:
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 4740] Mon Apr 02 15:07:53 2007
[Thr 4740] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 94
intno 20050900
make: multithreaded, ASCII, optimized
pid 2932
[Thr 4740] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 2932) [msxxserv.c 1824]
[Thr 4740] load acl file = D:\usr\sap\put\XYZ\SYS\global\ms_acl_info.DAT
[Thr 4740] MsGetOwnIpAddr: my host addresses are :
[Thr 4740] 1 : [10.10.10.68] houston (HOSTNAME)
[Thr 4740] 2 : [127.0.0.1] houston.monet.local (LOCALHOST)
[Thr 4740] Mon Apr 02 15:07:54 2007
[Thr 4740] MsHttpInit: full qualified hostname = houston.monet.local
[Thr 4740] HTTP logging is switch off
[Thr 4740] MsHttpOwnDomain: own domain[1] = monet.local
[Thr 4740] ms/icf_info_server : deleted
[Thr 4740] *** I listen to port sapmsSHDXYZ (3660) ***
[Thr 4740] CUSTOMER KEY: >B0790292062<
[Thr 4740] Mon Apr 02 15:08:54 2007
[Thr 4740] *** ERROR => MsSClientHandle: no server provides service ENQ (4), requested from houston_XYZ_60 [msxxserv.c 4679]
[Thr 4740] Mon Apr 02 15:19:35 2007
[Thr 4740] *** ERROR => MsSCheckConnections: no response from client C0 (10.10.10.68) after 300 secs received [msxxserv.c 3165]
[Thr 4740] *** ERROR => MsSCheckConnections: disconnect now [10.10.10.68] [msxxserv.c 3169]</b>
The dev_disp reads:
trc file: "dev_disp", trc level: 1, release: "700"
sysno 60
sid XYZ
systemid 560 (PC with Windows NT)
relno 7000
patchlevel 0
patchno 95
intno 20050900
make: multithreaded, ASCII, optimized
pid 4036
Mon Apr 02 15:07:53 2007
kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
length of sys_adm_ext is 360 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (60 4036) [dpxxdisp.c 1239]
shared lib "dw_xml.dll" version 95 successfully loaded
shared lib "dw_xtc.dll" version 95 successfully loaded
shared lib "dw_stl.dll" version 95 successfully loaded
shared lib "dw_gui.dll" version 95 successfully loaded
shared lib "dw_mdm.dll" version 95 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
Mon Apr 02 15:07:58 2007
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >houston_XYZ_60 <
DpShMCreate: sizeof(wp_adm) 19888 (904)
DpShMCreate: sizeof(tm_adm) 3605136 (17936)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm) 528048 (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm) 0 (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (72)
DpShMCreate: sizeof(vmc_adm) 0 (1280)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 05BF0040, size: 4240712)
DpShMCreate: allocated sys_adm at 05BF0040
DpShMCreate: allocated wp_adm at 05BF1A28
DpShMCreate: allocated tm_adm_list at 05BF67D8
DpShMCreate: allocated tm_adm at 05BF6808
DpShMCreate: allocated wp_ca_adm at 05F66A98
DpShMCreate: allocated appc_ca_adm at 05F6B0E8
DpShMCreate: allocated comm_adm at 05F6C858
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 05FED708
DpShMCreate: allocated gw_adm at 05FED748
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 05FED778
DpShMCreate: allocated wall_adm at 05FED780
MBUF state OFF
DpCommInitTable: init table for 500 entries
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Memory Reset disabled as NT default
<ES> 2039 blocks reserved for free list.
ES initialized.
WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c 12314]
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( houston) [dpxxdisp.c 11663]
DpStartStopMsg: send start message (myname is >houston_XYZ_60 <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 95
Release check o.K.
Mon Apr 02 15:08:38 2007
ERROR => W0 (pid 1084) died [dpxxdisp.c 14318]
ERROR => W1 (pid 4200) died [dpxxdisp.c 14318]
ERROR => W2 (pid 3316) died [dpxxdisp.c 14318]
ERROR => W3 (pid 5276) died [dpxxdisp.c 14318]
ERROR => W4 (pid 5348) died [dpxxdisp.c 14318]
ERROR => W5 (pid 3436) died [dpxxdisp.c 14318]
ERROR => W6 (pid 3920) died [dpxxdisp.c 14318]
ERROR => W7 (pid 4868) died [dpxxdisp.c 14318]
ERROR => W8 (pid 5380) died [dpxxdisp.c 14318]
ERROR => W9 (pid 4584) died [dpxxdisp.c 14318]
my types changed after wp death/restart 0x1f --> 0x1e
ERROR => W10 (pid 4188) died [dpxxdisp.c 14318]
my types changed after wp death/restart 0x1e --> 0x1c
ERROR => W11 (pid 2700) died [dpxxdisp.c 14318]
my types changed after wp death/restart 0x1c --> 0x18
ERROR => W12 (pid 4604) died [dpxxdisp.c 14318]
ERROR => W13 (pid 4916) died [dpxxdisp.c 14318]
ERROR => W14 (pid 4440) died [dpxxdisp.c 14318]
ERROR => W15 (pid 4544) died [dpxxdisp.c 14318]
ERROR => W16 (pid 1888) died [dpxxdisp.c 14318]
ERROR => W17 (pid 548) died [dpxxdisp.c 14318]
ERROR => W18 (pid 2800) died [dpxxdisp.c 14318]
ERROR => W19 (pid 2080) died [dpxxdisp.c 14318]
ERROR => W20 (pid 2888) died [dpxxdisp.c 14318]
my types changed after wp death/restart 0x18 --> 0x10
ERROR => W21 (pid 5572) died [dpxxdisp.c 14318]
my types changed after wp death/restart 0x10 --> 0x0
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1609
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Apr 02 15:08:48 2007
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long) Mon Apr 02 20:08:48 2007
========================
No Ty. Pid Status Cause Start Err Sem CPU Time Program Cl User Action Table
0 DIA 1084 Ended no 1 0 0
1 DIA 4200 Ended no 1 0 0
2 DIA 3316 Ended no 1 0 0
3 DIA 5276 Ended no 1 0 0
4 DIA 5348 Ended no 1 0 0
5 DIA 3436 Ended no 1 0 0
6 DIA 3920 Ended no 1 0 0
7 DIA 4868 Ended no 1 0 0
8 DIA 5380 Ended no 1 0 0
9 DIA 4584 Ended no 1 0 0
10 UPD 4188 Ended no 1 0 0
11 ENQ 2700 Ended no 1 0 0
12 BTC 4604 Ended no 1 0 0
13 BTC 4916 Ended no 1 0 0
14 BTC 4440 Ended no 1 0 0
15 BTC 4544 Ended no 1 0 0
16 BTC 1888 Ended no 1 0 0
17 BTC 548 Ended no 1 0 0
18 BTC 2800 Ended no 1 0 0
19 BTC 2080 Ended no 1 0 0
20 BTC 2888 Ended no 1 0 0
21 SPO 5572 Ended no 1 0 0
Dispatcher Queue Statistics Mon Apr 02 20:08:48 2007
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
1
2000
1
1
--------++++--
+
DIA
3
3
2000
3
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id 7
wake_evt_udp_now 0
wake events total 3, udp 3 (100%), shm 0 ( 0%)
since last update total 3, udp 3 (100%), shm 0 ( 0%)
Dump of tm_adm structure: Mon Apr 02 20:08:48 2007
=========================
Term uid man user term lastop mod wp ta a/i (modes)
Workprocess Comm. Area Blocks Mon Apr 02 20:08:48 2007
=============================
Slots: 300, Used: 1, Max: 0
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1609
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Apr 02 15:08:53 2007
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >houston_XYZ_60 < (normal)
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes
Stop gateway
killing process (2072) (SOFT_KILL)
Terminate gui connections
wait for end of work processes
wait for end of gateway
[DpProcDied] Process lives (PID:2072 HANDLE:1580)
waiting for termination of gateway ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1609
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Mon Apr 02 15:08:54 2007
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:2072 HANDLE:1580)
DpStartStopMsg: send stop message (myname is >houston_XYZ_60 <)
NiIMyHostName: hostname = 'houston'
AdGetSelfIdentRecord: > <
XYZvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
XYZvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=562,pac=1,MESG_IO)
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name -, type 4, key -
DpStartStopMsg: stop msg sent
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
NiIRead: read for hdl 2 timed out (0ms)
DpHalt: no more messages from the message server
DpHalt: send keepalive to synchronize with the message server
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=114,pac=1,MESG_IO)
MsINiWrite: sent 114 bytes
send msg (len 110+4) to name MSG_SERVER, type 0, key -
MsSndName: MS_NOOP ok
Send 4 bytes to MSG_SERVER
NiIRead: hdl 2 recv would block (errno=EAGAIN)
NiIPeek: peek successful for hdl 2 (r)
NiIRead: hdl 2 received data (rcd=114,pac=1,MESG_IO)
NiBufIIn: NIBUF len=114
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 114 bytes
MSG received, len 110+4, flag 3, from MSG_SERVER , typ 0, key -
Received 4 bytes from MSG_SERVER
Received opcode MS_NOOP from msg_server, reply MSOP_OK
MsOpReceive: ok
MsSendKeepalive : keepalive sent to message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
Mon Apr 02 15:08:55 2007
NiIPeek: peek for hdl 2 timed out (r; 1000ms)
NiIRead: read for hdl 2 timed out (1000ms)
DpHalt: no more messages from the message server
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 11976]
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiBufISelUpdate: new MODE -- (r-) for hdl 2 in set0
SiSelNSet: set events of sock 1488 to: ---
NiBufISelRemove: remove hdl 2 from set0
SiSelNRemove: removed sock 1488 (pos=2)
SiSelNRemove: removed sock 1488
NiSelIRemove: removed hdl 2
MBUF state OFF
AdGetSelfIdentRecord: > <
XYZvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
XYZvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
XYZvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/22
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 9)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 2 / sock 1488
NiBufIClose: clear extension for hdl 2
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 4036) [dpxxdisp.c 10333]
Good Bye .....
<b>The dev_w21 reads:
trc file: "dev_w21", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Mon Apr 02 15:08:01 2007
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\put\exe\dbmssslib.dll' ...
B Library 'D:\usr\sap\put\exe\dbmssslib.dll' loaded
B Version of 'D:\usr\sap\put\exe\dbmssslib.dll' is "700.08", patchlevel (0.87)
B New connection 0 created
M sysno 60
M sid XYZ
M systemid 560 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 95
M intno 20050900
M make: multithreaded, ASCII, optimized
M pid 5572
M
M kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
M length of sys_adm_ext is 360 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc21 5572) [dpxxdisp.c 1301]
I
I Mon Apr 02 15:08:02 2007
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 19888 (904)
M DpShMCreate: sizeof(tm_adm) 3605136 (17936)
M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
M DpShMCreate: sizeof(comm_adm) 528048 (1048)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (96)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1280)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 063F0040, size: 4240712)
M DpShMCreate: allocated sys_adm at 063F0040
M DpShMCreate: allocated wp_adm at 063F1A28
M DpShMCreate: allocated tm_adm_list at 063F67D8
M DpShMCreate: allocated tm_adm at 063F6808
M DpShMCreate: allocated wp_ca_adm at 06766A98
M DpShMCreate: allocated appc_ca_adm at 0676B0E8
M DpShMCreate: allocated comm_adm at 0676C858
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 067ED708
M DpShMCreate: allocated gw_adm at 067ED748
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 067ED778
M DpShMCreate: allocated wall_adm at 067ED780
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 21 initializing ....
X Using implementation view
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host houston
M
M Mon Apr 02 15:08:03 2007
M calling db_connect ...
C Thread ID:4020
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'D:\usr\sap\put\exe\dbmssslib.dll'
C dbmssslib.dll patch info
C patchlevel 0
C patchno 87
C patchcomment MSSQL: UTAB/ATAB/Dynp-access via clientside cursor (1002914)
C np:(local) connection used on houston
C CopyLocalParameters: dbuser is 'XYZ_shd'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Provider Release:9.00.1399.06
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Can't use MARS (on sql 8.0). Reconnecting without MARS functionality.
C Using Provider SQLNCLI
C Provider Release:9.00.1399.06
C Using Provider SQLNCLI
C CheckCodepageType: line 24329. hr: 0x80040e37 Invalid object name 'DBPROPERTIES'.
C sloledb.cpp [CheckCodepageType,line 24329]: Error/Message: (err 208, sev 16), Invalid object name 'DBPROPERTIES'.
C Procname: [CheckCodepageType -- no proc]
C Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 500 dynamic statements (2724000 bytes), total 29444052 bytes
C Initializing shared procedure name cache houston_XYZXYZ_XYZ_SHD_MEM.
C procedure cache created/attached
C PSP: 0 procedure names registered
C Connected to db server : [houston] server_used : [np:(local)], dbname: XYZ, dbuser: XYZ
C pn_id:houston_XYZXYZ_XYZ_SHD
C Not using MARS (on sql 8.0)
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20070402 150803 houston
C The IRow interface is supported by this OLEDB provider
C sloledb.cpp [ParamStmtExec,line 12988]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
C Procname: [##YshoustonXYZ00000055720000000001150803]
C sloledb.cpp [ParamStmtExec,line 12988]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.
C Procname: [##YshoustonXYZ00000055720000000001150803]
C ParamStmtExec failed. HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP 1 VERSION FROM SVERS ]
C Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 112156
C DbSlRead - Error 103 (dbcode 208) on open
C DbSlRead - <##YshoustonXYZ00000055720000000001150803>
C DbSlRead - Error 103 (dbcode 208) on fetch
C DbSlRead - <##YshoustonXYZ00000055720000000001150803>
B ***LOG BZA=> table SVERS does not exist on database [dblink#3 @ 1299] [dblink 1299 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 004096) [thxxhead.c 1426]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10240]
M
M Info for wp 21
M
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_SPOWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M vm = no VM
M
M *****************************************************************************
M *
M * LOCATION SAP-Server houston_XYZ_60 on host houston (wp 21)
M * ERROR ThInit: db_connect
M *
M * TIME Mon Apr 02 15:08:03 2007
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10439
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc21 5572) [dpnttool.c 327]</b>
On SDN there are many discussions about similar errors but none
of them fits our situation.
Please give your advice. Points will be given.
Thanks!Target SAP system is ADC
Enter the SAP instance number [59]:
? INSTANCE NUMBER =
Waiting for input since Mar 22, 2007 1:20:45 PM
> INSTANCE NUMBER = 59
Type of database system is MSS
>>>>>>>>>> Input Wizard <<<<<<<<<<
Please enter up to 24 mount points for CDs.
Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
? MOUNT POINT 01 =
? MOUNT POINT 02 =
? MOUNT POINT 03 =
? MOUNT POINT 04 =
? MOUNT POINT 05 =
? MOUNT POINT 06 =
Please enter up to 24 mount points for CDs.
Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
? MOUNT POINT 07 =
? MOUNT POINT 08 =
? MOUNT POINT 09 =
? MOUNT POINT 10 =
? MOUNT POINT 11 =
? MOUNT POINT 12 =
Please enter up to 24 mount points for CDs.
Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
? MOUNT POINT 13 =
? MOUNT POINT 14 =
? MOUNT POINT 15 =
? MOUNT POINT 16 =
? MOUNT POINT 17 =
? MOUNT POINT 18 =
Please enter up to 24 mount points for CDs.
Enter at least the mount point for the CD titled "Upgrade Master CD/DVD"
? MOUNT POINT 19 =
? MOUNT POINT 20 =
? MOUNT POINT 21 =
? MOUNT POINT 22 =
? MOUNT POINT 23 =
? MOUNT POINT 24 =
Waiting for input since Mar 22, 2007 1:20:49 PM
> MOUNT POINT 12 = D:\D12\SAP_CRM_5.0_SR2_Installation_Export
> MOUNT POINT 23 = D:\D23\51032247
> MOUNT POINT 18 = D:\D18\NW_2004s_SR2_liveCache_7.6.00_Bd._29
> MOUNT POINT 15 = D:\D15\NW_2004s_SR2_Upgrade_Master
> MOUNT POINT 09 = D:\D9
> MOUNT POINT 14 = D:\D14\SAP_CRM_5.0_SR2_Installation_Export
> MOUNT POINT 01 = D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export
> MOUNT POINT 08 = D:\D8\SAP_CRM_5.0_SR2_Languages
> MOUNT POINT 20 = D:\D20\NW_2004s_SR2_Languages
> MOUNT POINT 03 = C:\D3\SAP_CRM_5.0_SR2_Upgrade_Export
> MOUNT POINT 06 = C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86
> MOUNT POINT 10 = D:\D10
> MOUNT POINT 17 = D:\D17\51032257
> MOUNT POINT 21 = D:\D21\NW_2004s_SR2_Languages
> MOUNT POINT 19 = D:\D19\51032257
> MOUNT POINT 05 = C:\D5\SAP_CRM_5.0_SR2_Upgrade_Export
> MOUNT POINT 04 = C:\D4\SAP_CRM_5.0_SR2_Upgrade_Export
> MOUNT POINT 11 = D:\D11\SAP_CRM_5.0_SR2_Installation_Export
> MOUNT POINT 07 = D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master
> MOUNT POINT 24 = D:\D24
> MOUNT POINT 02 = C:\D2\SAP_CRM_5.0_SR2_Upgrade_Export
> MOUNT POINT 22 = D:\D22\NW_2004s_SR2_Languages
> MOUNT POINT 16 = D:\D16\BS_2005_SR2_SAP_Installation_Master
> MOUNT POINT 13 = D:\D13\SAP_CRM_5.0_SR2_Installation_Export
Reading data from "Upgrade Master CD/DVD"...
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL7000.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL7000.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL700X.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL700X.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS2.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS2.SAR successfully unpacked to D:\usr\sap\put.
Welcome to the SAP upgrade control program.
Important information for this upgrade is included
in the upgrade Note and further Notes mentioned therein.
Refer to the upgrade manual for the number of this note.
It is advisable to obtain this Note before starting any process
since it also contains important information about preparing
the upgrade.
It is essential that you get a current version of this Note
before starting the upgrade with SAPup. It contains a keyword
which is necessary to start the upgrade procedure.
Please look into the SAP Service Marketplace or, if not available,
use the form in your packet to request the upgrade Note.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:24:47 PM
> cancel
Connection to SAPup was closed
Target SAP system is ADC
Enter the SAP instance number [59]:
? INSTANCE NUMBER =
Waiting for input since Mar 22, 2007 1:28:34 PM
> INSTANCE NUMBER = 59
Type of database system is MSS
Reading data from "Upgrade Master CD"...
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL7000.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL7000.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL700X.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\DBINDEP\CTRL700X.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS2.SAR" to "D:\usr\sap\put" ...
Archive D:\D7\SAP_CRM_5.0_SR2_Upgrade_Master\UMN_WINDOWS_I386\MSS\UPTOOLS2.SAR successfully unpacked to D:\usr\sap\put.
Welcome to the SAP upgrade control program.
Important information for this upgrade is included
in the upgrade Note and further Notes mentioned therein.
Refer to the upgrade manual for the number of this note.
It is advisable to obtain this Note before starting any process
since it also contains important information about preparing
the upgrade.
It is essential that you get a current version of this Note
before starting the upgrade with SAPup. It contains a keyword
which is necessary to start the upgrade procedure.
Please look into the SAP Service Marketplace or, if not available,
use the form in your packet to request the upgrade Note.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:28:43 PM
> continue
SAP UPGRADE CONTROL PROGRAM
================================
This is SAPup version 7.00/2 upgrade to release
500 of BBPCRM
2005_1_700 of PI_BASIS
700 of SAP_ABA
700 of SAP_AP
700 of SAP_BASIS
700 of SAP_BW
2005_1_700 of ST-PI
Target SAP system is ADC, MSSQL database
SAPup started in PREPARE mode.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:28:50 PM
> continue
The following options are available:
select: Display screen for selecting PREPARE modules
status: Display the statuses of the PREPARE modules
exit: Exit PREPARE
help: Getting help about PREPARE
? select
? status
? exit
Waiting for input since Mar 22, 2007 1:28:54 PM
> select
Select the PREPARE modules
? name status mandatory
? Parameter input initial yes
? Initialization initial yes
? Import initial yes
? Extension initial yes
? Integration initial yes
? Installation initial yes
? General checks initial yes
? Activation checks initial yes
? Necessary checks for conversions initial yes
? Optional checks for conversions initial no
? Modification support initial no
? Pre-processing initial no
Waiting for input since Mar 22, 2007 1:28:56 PM
> Parameter input initial yes
You selected the following PREPARE modules:
Parameter input
execute: Execute the selected PREPARE modules.
Make sure that you have carried out the actions described in
D:\usr\sap\put\log\CHECKS.LOG before continuing.
(Note: The contents of file CHECKS.LOG are saved
in D:\usr\sap\put\log\CHECKS.SAV)
select: Display screen for selecting PREPARE modules.
exit: Exit PREPARE.
help: Getting help about PREPARE modules.
? execute
? select
? exit
Waiting for input since Mar 22, 2007 1:28:59 PM
> execute
Execution of PREPARE module Parameter input begins at 20070322142901
>> 14:29:01 PREPARE: START OF PHASE BEGIN_PRE
Generating html phase list files 'phase_toc.html' and 'phaselist.html'
>> 14:29:01 PREPARE: END OF PHASE BEGIN_PRE
>> 14:29:01 PREPARE: START OF PHASE KEY_CHK
Correction package 'D:\usr\sap\put\FIX_CRM50SR2.UPG' found, extracting to 'D:\usr\sap\put'
Archive successfully unpacked.
Enter the SAPup keyword of note 961511
? SAPup keyword =
Waiting for input since Mar 22, 2007 1:29:02 PM
> SAPup keyword = 19327784
>> 14:37:23 PREPARE: END OF PHASE KEY_CHK
>> 14:37:23 PREPARE: START OF PHASE EXTRACTKRN_PRE
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPMMC.SAR" to "D:\usr\sap\put\exe" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPMMC.SAR successfully unpacked to D:\usr\sap\put\exe.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\UNINSTSAP.EXE" to "D:\usr\sap\put\exe" ...
Done.
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPEXE.SAR" to "D:\usr\sap\put\exe" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPEXE.SAR successfully unpacked to D:\usr\sap\put\exe.
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\MSS\SAPEXEDB.SAR" to "D:\usr\sap\put\exe" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\MSS\SAPEXEDB.SAR successfully unpacked to D:\usr\sap\put\exe.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\IGSEXE.SAR" to "D:\usr\sap\put\exe" ...
Done.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\IGSHELPER.SAR" to "D:\usr\sap\put\exe" ...
Done.
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPMMC.SAR" to "D:\usr\sap\put\exenew" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPMMC.SAR successfully unpacked to D:\usr\sap\put\exenew.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\UNINSTSAP.EXE" to "D:\usr\sap\put\exenew" ...
Done.
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPEXE.SAR" to "D:\usr\sap\put\exenew" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\SAPEXE.SAR successfully unpacked to D:\usr\sap\put\exenew.
Extracting archive "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\MSS\SAPEXEDB.SAR" to "D:\usr\sap\put\exenew" ...
Archive C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\MSS\SAPEXEDB.SAR successfully unpacked to D:\usr\sap\put\exenew.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\IGSEXE.SAR" to "D:\usr\sap\put\exenew" ...
Done.
Copying file "C:\D6\NW_2004s_SR2_Kernel_WINDOWS__LNX_X86\KN_WINDOWS_I386_AUPG\DBINDEP\IGSHELPER.SAR" to "D:\usr\sap\put\exenew" ...
Done.
>> 14:40:10 PREPARE: END OF PHASE EXTRACTKRN_PRE
>> 14:40:10 PREPARE: START OF PHASE INITPUT_PRE
Supply the following information:
Confirm the name of your SAP system:
? SAP SYSTEM ID =
The hostname of your central SAP server:
? SAP SYSTEM HOST =
Enter the SAP instance number:
? INSTANCE NUMBER =
Waiting for input since Mar 22, 2007 1:40:10 PM
> INSTANCE NUMBER = 59
> SAP SYSTEM HOST = damascus
> SAP SYSTEM ID = ADC
The system identifier of your database:
? DATABASE ID =
The hostname of your database server:
? DATABASE HOST =
Waiting for input since Mar 22, 2007 1:43:59 PM
> DATABASE HOST = damascus
> DATABASE ID = ADC
Executing script MSSCONCHECK ...
Supply the following information:
The password for SAP user DDIC in client 000
(may be 19920706):
? DDIC PASSWORD =
Verify password for SAP user DDIC:
? DDIC PASSWORD =
Waiting for input since Mar 22, 2007 1:44:03 PM
> DDIC PASSWORD = <hidden input>
> DDIC PASSWORD = <hidden input>
The hostname of your batch server:
? BATCH HOST =
Waiting for input since Mar 22, 2007 1:44:14 PM
> BATCH HOST = damascus
Supply the following information:
The maximum number of parallel processes during uptime:
? MAXIMUM UPTIME PROCESSES =
The number of parallel import processes:
? R3TRANS PROCESSES =
The maximum profile value of "bufreftime":
? MAXIMUM SYNC TIME =
Waiting for input since Mar 22, 2007 1:44:16 PM
> R3TRANS PROCESSES = 3
> MAXIMUM SYNC TIME = 120
> MAXIMUM UPTIME PROCESSES = 1
The password for Operating System account .\SAPServiceADC:
? PASSWORD =
Verification of the password for Operating System account .\SAPServiceADC:
? PASSWORD =
Waiting for input since Mar 22, 2007 1:44:19 PM
> PASSWORD = <hidden input>
> PASSWORD = <hidden input>
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
Executing script MSSUPGSPS ...
Executing script MSSINCHK ...
>> 14:44:43 PREPARE: END OF PHASE INITPUT_PRE
>> 14:44:43 PREPARE: START OF PHASE DBCHK_PRE
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
Is there more than one system running in this database?
(MCOD: Multiple components in one database)
? no
? yes
Waiting for input since Mar 22, 2007 1:44:45 PM
> no
>> 14:44:49 PREPARE: END OF PHASE DBCHK_PRE
>> 14:44:49 PREPARE: START OF PHASE CONFCHK_IMP
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
>> 14:44:50 PREPARE: END OF PHASE CONFCHK_IMP
>> 14:44:50 PREPARE: START OF PHASE SOLMAN_CHK
The SAP Solution Manager Key is required for the upgrade.
Further informations can be found in the upgrade guide,
the SAP Service Marketplace and SAP note 805390!
? continue
? cancel
Waiting for input since Mar 22, 2007 1:44:50 PM
> continue
? SAP Solution Manager Key =
Waiting for input since Mar 22, 2007 1:44:53 PM
> SAP Solution Manager Key = 12D8B10981
>> 14:45:14 PREPARE: END OF PHASE SOLMAN_CHK
>> 14:45:14 PREPARE: START OF PHASE CHKSYSTYPE
>> 14:45:14 PREPARE: END OF PHASE CHKSYSTYPE
>> 14:45:14 PREPARE: START OF PHASE HIAV_CHK
>> 14:45:14 PREPARE: END OF PHASE HIAV_CHK
>> 14:45:15 PREPARE: START OF PHASE J2EE_CHK1
>> 14:45:15 PREPARE: END OF PHASE J2EE_CHK1
>> 14:45:15 PREPARE: START OF PHASE REQ_J2EEUPG
>> 14:45:15 PREPARE: END OF PHASE REQ_J2EEUPG
>> 14:45:15 PREPARE: START OF PHASE SETSYNC_PREP_STARTED
>> 14:45:15 PREPARE: END OF PHASE SETSYNC_PREP_STARTED
>> 14:45:15 PREPARE: START OF PHASE REQ_READNOTE
>> 14:45:15 PREPARE: END OF PHASE REQ_READNOTE
>> 14:45:15 PREPARE: START OF PHASE INIT_CBU
>> 14:45:15 PREPARE: END OF PHASE INIT_CBU
>> 14:45:15 PREPARE: START OF PHASE CHECKGROUP_END0
Execution of PREPARE module Parameter input ends at 20070322144515
Execution of the selected PREPARE modules finished
with the statuses as follows:
'Parameter input' status: succeeded
Please see file D:\usr\sap\put\log\CHECKS.LOG
for the actions which have to be performed.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:45:15 PM
> continue
The following options are available:
select: Display screen for selecting PREPARE modules
status: Display the statuses of the PREPARE modules
exit: Exit PREPARE
help: Getting help about PREPARE
? select
? status
? exit
Waiting for input since Mar 22, 2007 1:45:23 PM
> select
Select the PREPARE modules
? name status mandatory
? Parameter input succeeded yes
? Initialization initial yes
? Import initial yes
? Extension initial yes
? Integration initial yes
? Installation initial yes
? General checks initial yes
? Activation checks initial yes
? Necessary checks for conversions initial yes
? Optional checks for conversions initial no
? Modification support initial no
? Pre-processing initial no
Waiting for input since Mar 22, 2007 1:45:26 PM
> Initialization initial yes
You selected the following PREPARE modules:
Initialization
execute: Execute the selected PREPARE modules.
Make sure that you have carried out the actions described in
D:\usr\sap\put\log\CHECKS.LOG before continuing.
(Note: The contents of file CHECKS.LOG are saved
in D:\usr\sap\put\log\CHECKS.SAV)
select: Display screen for selecting PREPARE modules.
exit: Exit PREPARE.
help: Getting help about PREPARE modules.
? execute
? select
? exit
? display CHECKS.LOG
Waiting for input since Mar 22, 2007 1:45:30 PM
> execute
Execution of PREPARE module Initialization begins at 20070322144532
>> 14:45:32 PREPARE: START OF PHASE INITCURENV
>> 14:45:32 PREPARE: END OF PHASE INITCURENV
>> 14:45:32 PREPARE: START OF PHASE DBCHK_INI
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getdbinfo ADC
>> 14:45:34 PREPARE: END OF PHASE DBCHK_INI
>> 14:45:34 PREPARE: START OF PHASE RFCCHK_INI
>> 14:45:34 PREPARE: END OF PHASE RFCCHK_INI
>> 14:45:34 PREPARE: START OF PHASE VERSCHK_INI
>> 14:45:34 PREPARE: END OF PHASE VERSCHK_INI
>> 14:45:34 PREPARE: START OF PHASE VALCHK_INI
>> 14:45:35 PREPARE: END OF PHASE VALCHK_INI
>> 14:45:35 PREPARE: START OF PHASE TOOLVERSION_INI
>> 14:45:36 PREPARE: END OF PHASE TOOLVERSION_INI
>> 14:45:36 PREPARE: START OF PHASE UNICODE_CHK_PRE
>> 14:45:36 PREPARE: END OF PHASE UNICODE_CHK_PRE
>> 14:45:36 PREPARE: START OF PHASE TOOLVERSION_UPG1
>> 14:46:00 PREPARE: END OF PHASE TOOLVERSION_UPG1
>> 14:46:00 PREPARE: START OF PHASE DBCONNCHK_INI
Checking DB connect with 'D:\usr\sap\put\exe\R3trans.exe'.
>> 14:46:00 PREPARE: END OF PHASE DBCONNCHK_INI
>> 14:46:00 PREPARE: START OF PHASE SETSYNC_INFO_FINISHED
>> 14:46:00 PREPARE: END OF PHASE SETSYNC_INFO_FINISHED
>> 14:46:00 PREPARE: START OF PHASE UCMIG_DECISION
Your system is configured as a non-Unicode SCP (Single Code Page) configuration.
If you plan to perform a Unicode Conversion after the upgrade, you may choose to perform a combined
Upgrade and Unicode Conversion.
In this case, several of the migration preparation steps can be done already on the start release
or on the upgrade shadow system.
For further information, please refer to OSS note 928729.
Do you want to perform a combined Upgrade and Unicode Conversion?
? Yes
? No
Waiting for input since Mar 22, 2007 1:46:06 PM
> No
>> 14:48:04 PREPARE: END OF PHASE UCMIG_DECISION
>> 14:48:04 PREPARE: START OF PHASE CLNT_CHK_INI
>> 14:48:09 PREPARE: END OF PHASE CLNT_CHK_INI
>> 14:48:09 PREPARE: START OF PHASE PATCH_CHK1
>> 14:48:15 PREPARE: END OF PHASE PATCH_CHK1
>> 14:48:15 PREPARE: START OF PHASE INTCHK_INI
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getddxttent ADC
running D:\usr\sap\ADC\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\DEFAULT.TPP getddxtfent ADC
>> 14:48:15 PREPARE: END OF PHASE INTCHK_INI
>> 14:48:15 PREPARE: START OF PHASE ADJ_CNTRANS
Calling R3trans to import 'RSUPDTEC.60X'.
Waiting 130 seconds for buffer synchronization ...
working ...
>> 14:50:38 PREPARE: END OF PHASE ADJ_CNTRANS
>> 14:50:38 PREPARE: START OF PHASE INIT_CNTRANS
>> 14:50:38 PREPARE: END OF PHASE INIT_CNTRANS
>> 14:50:38 PREPARE: START OF PHASE CNTRANS_PRE
>> 14:50:38 PREPARE: END OF PHASE CNTRANS_PRE
>> 14:50:38 PREPARE: START OF PHASE DMPSPC_INI
>> 14:50:38 PREPARE: END OF PHASE DMPSPC_INI
>> 14:50:38 PREPARE: START OF PHASE JOB_RSDB4090
>> 14:50:38 PREPARE: END OF PHASE JOB_RSDB4090
>> 14:50:38 PREPARE: START OF PHASE CHK_DB6_REG_PRE
>> 14:50:38 PREPARE: END OF PHASE CHK_DB6_REG_PRE
>> 14:50:39 PREPARE: START OF PHASE CHK_DB6_PAR_INI
>> 14:50:39 PREPARE: END OF PHASE CHK_DB6_PAR_INI
>> 14:50:39 PREPARE: START OF PHASE SPACECHK_INI
Executing script MSSSPACE ...
>> 14:50:39 PREPARE: END OF PHASE SPACECHK_INI
>> 14:50:39 PREPARE: START OF PHASE KRNCHK_DEST
>> 14:50:39 PREPARE: END OF PHASE KRNCHK_DEST
>> 14:50:39 PREPARE: START OF PHASE DBPREP_CHK
>> 14:50:39 PREPARE: END OF PHASE DBPREP_CHK
>> 14:50:39 PREPARE: START OF PHASE EXECCV
>> 14:50:44 PREPARE: END OF PHASE EXECCV
>> 14:50:44 PREPARE: START OF PHASE EXECAV
>> 14:50:50 PREPARE: END OF PHASE EXECAV
>> 14:50:50 PREPARE: START OF PHASE COMPINFO_INI
>> 14:50:50 PREPARE: END OF PHASE COMPINFO_INI
>> 14:50:50 PREPARE: START OF PHASE ADDON_CHK
>> 14:50:50 PREPARE: END OF PHASE ADDON_CHK
>> 14:50:50 PREPARE: START OF PHASE ADDON_INFO
>> 14:50:50 PREPARE: END OF PHASE ADDON_INFO
>> 14:50:50 PREPARE: START OF PHASE ADDON_SPEC1
>> 14:50:55 PREPARE: END OF PHASE ADDON_SPEC1
>> 14:50:56 PREPARE: START OF PHASE ADDON_TREAS
>> 14:50:56 PREPARE: END OF PHASE ADDON_TREAS
>> 14:50:56 PREPARE: START OF PHASE ADDON_WFM
>> 14:51:01 PREPARE: END OF PHASE ADDON_WFM
>> 14:51:01 PREPARE: START OF PHASE ADDON_DMC
>> 14:51:01 PREPARE: END OF PHASE ADDON_DMC
>> 14:51:01 PREPARE: START OF PHASE ACE_CHK
>> 14:51:01 PREPARE: END OF PHASE ACE_CHK
>> 14:51:02 PREPARE: START OF PHASE CRM_BILL
>> 14:51:02 PREPARE: END OF PHASE CRM_BILL
>> 14:51:02 PREPARE: START OF PHASE PR_DBPAR
>> 14:51:02 PREPARE: END OF PHASE PR_DBPAR
>> 14:51:02 PREPARE: START OF PHASE CHECKGROUP_END1
Execution of PREPARE module Initialization ends at 20070322145102
Execution of the selected PREPARE modules finished
with the statuses as follows:
'Initialization' status: succeeded
Please see file D:\usr\sap\put\log\CHECKS.LOG
for the actions which have to be performed.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:51:02 PM
> continue
The following options are available:
select: Display screen for selecting PREPARE modules
status: Display the statuses of the PREPARE modules
exit: Exit PREPARE
help: Getting help about PREPARE
? select
? status
? exit
Waiting for input since Mar 22, 2007 1:51:41 PM
> continue
Select the PREPARE modules
? name status mandatory
? Parameter input succeeded yes
? Initialization succeeded yes
? Import initial yes
? Extension initial yes
? Integration initial yes
? Installation initial yes
? General checks initial yes
? Activation checks initial yes
? Necessary checks for conversions initial yes
? Optional checks for conversions initial no
? Modification support initial no
? Pre-processing initial no
Waiting for input since Mar 22, 2007 1:51:41 PM
SAP UPGRADE CONTROL PROGRAM
================================
This is SAPup version 7.00/2 upgrade to release
500 of BBPCRM
2005_1_700 of PI_BASIS
700 of SAP_ABA
700 of SAP_AP
700 of SAP_BASIS
700 of SAP_BW
2005_1_700 of ST-PI
Target SAP system is ADC, MSSQL database
SAPup started in PREPARE mode.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:58:46 PM
> continue
The following options are available:
select: Display screen for selecting PREPARE modules
status: Display the statuses of the PREPARE modules
exit: Exit PREPARE
help: Getting help about PREPARE
? select
? status
? exit
Waiting for input since Mar 22, 2007 1:58:53 PM
> select
Select the PREPARE modules
? name status mandatory
? Parameter input succeeded yes
? Initialization succeeded yes
? Import initial yes
? Extension initial yes
? Integration initial yes
? Installation initial yes
? General checks initial yes
? Activation checks initial yes
? Necessary checks for conversions initial yes
? Optional checks for conversions initial no
? Modification support initial no
? Pre-processing initial no
Waiting for input since Mar 22, 2007 1:58:56 PM
> Import initial yes
You selected the following PREPARE modules:
Import
execute: Execute the selected PREPARE modules.
Make sure that you have carried out the actions described in
D:\usr\sap\put\log\CHECKS.LOG before continuing.
(Note: The contents of file CHECKS.LOG are saved
in D:\usr\sap\put\log\CHECKS.SAV)
select: Display screen for selecting PREPARE modules.
exit: Exit PREPARE.
help: Getting help about PREPARE modules.
? execute
? select
? exit
? display CHECKS.LOG
Waiting for input since Mar 22, 2007 1:59:00 PM
> execute
Execution of PREPARE module Import begins at 20070322145902
>> 14:59:02 PREPARE: START OF PHASE REQIMPORT
The PREPARE module Import will be started now.
During this module programs, structures, and table entries
required by PREPARE are imported (the socalled "tool import").
Note: This can cause a loss of performance in R/3
In rare cases, a concurrent transport via the transport directory
may disturb the tool import. Please avoid any concurrent import
during this PREPARE module.
? continue
? cancel
Waiting for input since Mar 22, 2007 1:59:02 PM
> continue
>> 14:59:05 PREPARE: END OF PHASE REQIMPORT
>> 14:59:05 PREPARE: START OF PHASE READDATA
Trying to find archive files ...
Extracting archive "D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC7000.SAR" to "D:\usr\sap\put" ...
Archive D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC7000.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC700X.SAR" to "D:\usr\sap\put" ...
Archive D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC700X.SAR successfully unpacked to D:\usr\sap\put.
Extracting archive "D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC_SP.SAR" to "D:\usr\sap\put" ...
Archive D:\D1\SAP_CRM_5.0_SR2_Upgrade_Export\UPG1\DBINDEP\MISC_SP.SAR successfully unpacked to D:\usr\sap\put.
Trying to find archive files ...
Extracting archive "C:\D2\SAP_CRM_5.0_SR2_Upgrade_Export\UPG2\DBINDEP\MISC700I.SAR" to "D:\usr\sap\put" ...
Archive C:\D2\SAP_CRM_5.0_SR2_Upgrade_Export\UPG2\DBINDEP\MISC700I.SAR successfully unpacked to D:\usr\sap\put.
>> 14:59:40 PREPARE: END OF PHASE READDATA
>> 14:59:40 PREPARE: START OF PHASE READDATA_EXT
Trying to find archive files ...
>> 14:59:41 PREPARE: END OF PHASE READDATA_EXT
>> 14:59:41 PREPARE: START OF PHASE TOOLFIX_CHK
Correction package 'D:\usr\sap\put\FIX_CRM50SR2.UPG' found, extracting to 'D:\usr\sap\put'
Archive successfully unpacked.
>> 14:59:42 PREPARE: END OF PHASE TOOLFIX_CHK
>> 14:59:42 PREPARE: START OF PHASE CPYFIL0_CBU
>> 14:59:42 PREPARE: END OF P -
DB connect error in pre-migration check (EP5.0 SP6- EP6 SP16)
Hello,
I am working on migration (EP 5.0 SP 6--> EP 6.0 SP 16).
I have created a EP 5 System ,While I am checking for connectivity, (http://nw04:5000/sp) it displays an error message. Here is a string I have used for connection.
URL: jdbc:sap:sqlserver://btep-5:1433;DatabaseName=TTPSys
Driver Class Name: com.sap.portal.jdbc.sqlserver.SQLServerDriver
<b>Error message start:</b>----
Test connection to source DB failed, please check Database parameters in EP5.0 system
exception occured - could not check P310_SUPPORTED_LANGUAGES
Tue Aug 08 17:01:31 GMT+05:30 2006 : java.lang.ClassNotFoundException
at com.sapportals.utilities.analyzer.deploy.JarClassLoader.findClass(JarClassLoader.java:82)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.createConnection(checkDBConnection.java:82)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.checkConnectionToDB(checkDBConnection.java:58)
at com.sap.portal.ep5tonw04migration.premigration.checkDBConnection.analyze(checkDBConnection.java:30)
at com.sapportals.utilities.analyzer.PluginManager.analyze(PluginManager.java:281)
at com.sapportals.utilities.analyzer.PluginManager.run(PluginManager.java:995)
at java.lang.Thread.run(Thread.java:534)
Tue Aug 08 17:01:31 GMT+05:30 2006 : null
<b>Error message END:</b>----
Does any one have idea what could be the reason?
Regards
Sunil KulkarniHello Nageshwar,
the likely root cause of this issue is the lack of permissions for the user on the shadow instance.
Please review note #592514 and check your users' rights accordingly.
Best regards,
Tomas Black -
Problem with JQuery tab after migrated to APEX 4.0
My test application hosted on apex.oracle.com is using JQuery tab function and it is running well with APEX 3.2.1.
And now after the migration to APEX 4.0, it can not display the tab anymore.
Any idea how to solve this problem?
Thanks a lot.<html lang="&BROWSER_LANGUAGE." xmlns:htmldb="http://htmldb.oracle.com">
<head>
<title>#TITLE#</title>
<link rel="stylesheet" href="#IMAGE_PREFIX#themes/theme_15/theme_3_1.css" type="text/css" />
<style type="text/css">
* jQuery UI CSS Framework
* Copyright (c) 2009 AUTHORS.txt (http://jqueryui.com/about)
* Dual licensed under the MIT (MIT-LICENSE.txt) and GPL (GPL-LICENSE.txt) licenses.
/* Layout helpers
.ui-helper-hidden { display: none; }
.ui-helper-hidden-accessible { position: absolute; left: -99999999px; }
.ui-helper-reset { margin: 0; padding: 0; border: 0; outline: 0; line-height: 1.3; text-decoration: none; font-size: 100%; list-style: none; }
.ui-helper-clearfix:after { content: "."; display: block; height: 0; clear: both; visibility: hidden; }
.ui-helper-clearfix { display: inline-block; }
/* required comment for clearfix to work in Opera \*/
* html .ui-helper-clearfix { height:1%; }
.ui-helper-clearfix { display:block; }
/* end clearfix */
.ui-helper-zfix { width: 100%; height: 100%; top: 0; left: 0; position: absolute; opacity: 0; filter:Alpha(Opacity=0); }
/* Interaction Cues
.ui-state-disabled { cursor: default !important; }
/* Icons
/* states and images */
.ui-icon { display: block; text-indent: -99999px; overflow: hidden; background-repeat: no-repeat; }
/* Misc visuals
/* Overlays */
.ui-widget-overlay { position: absolute; top: 0; left: 0; width: 100%; height: 100%; }
* jQuery UI CSS Framework
* Copyright (c) 2009 AUTHORS.txt (http://jqueryui.com/about)
* Dual licensed under the MIT (MIT-LICENSE.txt) and GPL (GPL-LICENSE.txt) licenses.
* To view and modify this theme, visit http://jqueryui.com/themeroller/?ffDefault=Lucida%20Grande,%20Lucida%20Sans,%20Arial,%20sans-serif&fwDefault=bold&fsDefault=1.1em&cornerRadius=5px&bgColorHeader=5c9ccc&bgTextureHeader=12_gloss_wave.png&bgImgOpacityHeader=55&borderColorHeader=4297d7&fcHeader=ffffff&iconColorHeader=d8e7f3&bgColorContent=fcfdfd&bgTextureContent=06_inset_hard.png&bgImgOpacityContent=100&borderColorContent=a6c9e2&fcContent=222222&iconColorContent=469bdd&bgColorDefault=dfeffc&bgTextureDefault=02_glass.png&bgImgOpacityDefault=85&borderColorDefault=c5dbec&fcDefault=2e6e9e&iconColorDefault=6da8d5&bgColorHover=d0e5f5&bgTextureHover=02_glass.png&bgImgOpacityHover=75&borderColorHover=79b7e7&fcHover=1d5987&iconColorHover=217bc0&bgColorActive=f5f8f9&bgTextureActive=06_inset_hard.png&bgImgOpacityActive=100&borderColorActive=79b7e7&fcActive=e17009&iconColorActive=f9bd01&bgColorHighlight=fbec88&bgTextureHighlight=01_flat.png&bgImgOpacityHighlight=55&borderColorHighlight=fad42e&fcHighlight=363636&iconColorHighlight=2e83ff&bgColorError=fef1ec&bgTextureError=02_glass.png&bgImgOpacityError=95&borderColorError=cd0a0a&fcError=cd0a0a&iconColorError=cd0a0a&bgColorOverlay=aaaaaa&bgTextureOverlay=01_flat.png&bgImgOpacityOverlay=0&opacityOverlay=30&bgColorShadow=aaaaaa&bgTextureShadow=01_flat.png&bgImgOpacityShadow=0&opacityShadow=30&thicknessShadow=8px&offsetTopShadow=-8px&offsetLeftShadow=-8px&cornerRadiusShadow=8px
/* Component containers
.ui-widget { font-family: Lucida Grande, Lucida Sans, Arial, sans-serif; font-size: 1.1em; }
.ui-widget input, .ui-widget select, .ui-widget textarea, .ui-widget button { font-family: Lucida Grande, Lucida Sans, Arial, sans-serif; font-size: 1em; }
.ui-widget-content { border: 1px solid #a6c9e2; background: #fcfdfd url(images/ui-bg_inset-hard_100_fcfdfd_1x100.png) 50% bottom repeat-x; color: #222222; }
.ui-widget-content a { color: #222222; }
.ui-widget-header { border: 1px solid #4297d7; background: #5c9ccc url(images/ui-bg_gloss-wave_55_5c9ccc_500x100.png) 50% 50% repeat-x; color: #ffffff; font-weight: bold; }
.ui-widget-header a { color: #ffffff; }
/* Interaction states
.ui-state-default, .ui-widget-content .ui-state-default { border: 1px solid #c5dbec; background: #dfeffc url(images/ui-bg_glass_85_dfeffc_1x400.png) 50% 50% repeat-x; font-weight: bold; color: #2e6e9e; outline: none; }
.ui-state-default a, .ui-state-default a:link, .ui-state-default a:visited { color: #2e6e9e; text-decoration: none; outline: none; }
.ui-state-hover, .ui-widget-content .ui-state-hover, .ui-state-focus, .ui-widget-content .ui-state-focus { border: 1px solid #79b7e7; background: #d0e5f5 url(images/ui-bg_glass_75_d0e5f5_1x400.png) 50% 50% repeat-x; font-weight: bold; color: #1d5987; outline: none; }
.ui-state-hover a, .ui-state-hover a:hover { color: #1d5987; text-decoration: none; outline: none; }
.ui-state-active, .ui-widget-content .ui-state-active { border: 1px solid #79b7e7; background: #f5f8f9 url(images/ui-bg_inset-hard_100_f5f8f9_1x100.png) 50% 50% repeat-x; font-weight: bold; color: #e17009; outline: none; }
.ui-state-active a, .ui-state-active a:link, .ui-state-active a:visited { color: #e17009; outline: none; text-decoration: none; }
/* Interaction Cues
.ui-state-highlight, .ui-widget-content .ui-state-highlight {border: 1px solid #fad42e; background: #fbec88 url(images/ui-bg_flat_55_fbec88_40x100.png) 50% 50% repeat-x; color: #363636; }
.ui-state-highlight a, .ui-widget-content .ui-state-highlight a { color: #363636; }
.ui-state-error, .ui-widget-content .ui-state-error {border: 1px solid #cd0a0a; background: #fef1ec url(images/ui-bg_glass_95_fef1ec_1x400.png) 50% 50% repeat-x; color: #cd0a0a; }
.ui-state-error a, .ui-widget-content .ui-state-error a { color: #cd0a0a; }
.ui-state-error-text, .ui-widget-content .ui-state-error-text { color: #cd0a0a; }
.ui-state-disabled, .ui-widget-content .ui-state-disabled { opacity: .35; filter:Alpha(Opacity=35); background-image: none; }
.ui-priority-primary, .ui-widget-content .ui-priority-primary { font-weight: bold; }
.ui-priority-secondary, .ui-widget-content .ui-priority-secondary { opacity: .7; filter:Alpha(Opacity=70); font-weight: normal; }
/* Icons
/* states and images */
.ui-icon { width: 16px; height: 16px; background-image: url(images/ui-icons_469bdd_256x240.png); }
.ui-widget-content .ui-icon {background-image: url(images/ui-icons_469bdd_256x240.png); }
.ui-widget-header .ui-icon {background-image: url(images/ui-icons_d8e7f3_256x240.png); }
.ui-state-default .ui-icon { background-image: url(images/ui-icons_6da8d5_256x240.png); }
.ui-state-hover .ui-icon, .ui-state-focus .ui-icon {background-image: url(images/ui-icons_217bc0_256x240.png); }
.ui-state-active .ui-icon {background-image: url(images/ui-icons_f9bd01_256x240.png); }
.ui-state-highlight .ui-icon {background-image: url(images/ui-icons_2e83ff_256x240.png); }
.ui-state-error .ui-icon, .ui-state-error-text .ui-icon {background-image: url(images/ui-icons_cd0a0a_256x240.png); }
/* positioning */
.ui-icon-carat-1-n { background-position: 0 0; }
.ui-icon-carat-1-ne { background-position: -16px 0; }
.ui-icon-carat-1-e { background-position: -32px 0; }
.ui-icon-carat-1-se { background-position: -48px 0; }
.ui-icon-carat-1-s { background-position: -64px 0; }
.ui-icon-carat-1-sw { background-position: -80px 0; }
.ui-icon-carat-1-w { background-position: -96px 0; }
.ui-icon-carat-1-nw { background-position: -112px 0; }
.ui-icon-carat-2-n-s { background-position: -128px 0; }
.ui-icon-carat-2-e-w { background-position: -144px 0; }
.ui-icon-triangle-1-n { background-position: 0 -16px; }
.ui-icon-triangle-1-ne { background-position: -16px -16px; }
.ui-icon-triangle-1-e { background-position: -32px -16px; }
.ui-icon-triangle-1-se { background-position: -48px -16px; }
.ui-icon-triangle-1-s { background-position: -64px -16px; }
.ui-icon-triangle-1-sw { background-position: -80px -16px; }
.ui-icon-triangle-1-w { background-position: -96px -16px; }
.ui-icon-triangle-1-nw { background-position: -112px -16px; }
.ui-icon-triangle-2-n-s { background-position: -128px -16px; }
.ui-icon-triangle-2-e-w { background-position: -144px -16px; }
.ui-icon-arrow-1-n { background-position: 0 -32px; }
.ui-icon-arrow-1-ne { background-position: -16px -32px; }
.ui-icon-arrow-1-e { background-position: -32px -32px; }
.ui-icon-arrow-1-se { background-position: -48px -32px; }
.ui-icon-arrow-1-s { background-position: -64px -32px; }
.ui-icon-arrow-1-sw { background-position: -80px -32px; }
.ui-icon-arrow-1-w { background-position: -96px -32px; }
.ui-icon-arrow-1-nw { background-position: -112px -32px; }
.ui-icon-arrow-2-n-s { background-position: -128px -32px; }
.ui-icon-arrow-2-ne-sw { background-position: -144px -32px; }
.ui-icon-arrow-2-e-w { background-position: -160px -32px; }
.ui-icon-arrow-2-se-nw { background-position: -176px -32px; }
.ui-icon-arrowstop-1-n { background-position: -192px -32px; }
.ui-icon-arrowstop-1-e { background-position: -208px -32px; }
.ui-icon-arrowstop-1-s { background-position: -224px -32px; }
.ui-icon-arrowstop-1-w { background-position: -240px -32px; }
.ui-icon-arrowthick-1-n { background-position: 0 -48px; }
.ui-icon-arrowthick-1-ne { background-position: -16px -48px; }
.ui-icon-arrowthick-1-e { background-position: -32px -48px; }
.ui-icon-arrowthick-1-se { background-position: -48px -48px; }
.ui-icon-arrowthick-1-s { background-position: -64px -48px; }
.ui-icon-arrowthick-1-sw { background-position: -80px -48px; }
.ui-icon-arrowthick-1-w { background-position: -96px -48px; }
.ui-icon-arrowthick-1-nw { background-position: -112px -48px; }
.ui-icon-arrowthick-2-n-s { background-position: -128px -48px; }
.ui-icon-arrowthick-2-ne-sw { background-position: -144px -48px; }
.ui-icon-arrowthick-2-e-w { background-position: -160px -48px; }
.ui-icon-arrowthick-2-se-nw { background-position: -176px -48px; }
.ui-icon-arrowthickstop-1-n { background-position: -192px -48px; }
.ui-icon-arrowthickstop-1-e { background-position: -208px -48px; }
.ui-icon-arrowthickstop-1-s { background-position: -224px -48px; }
.ui-icon-arrowthickstop-1-w { background-position: -240px -48px; }
.ui-icon-arrowreturnthick-1-w { background-position: 0 -64px; }
.ui-icon-arrowreturnthick-1-n { background-position: -16px -64px; }
.ui-icon-arrowreturnthick-1-e { background-position: -32px -64px; }
.ui-icon-arrowreturnthick-1-s { background-position: -48px -64px; }
.ui-icon-arrowreturn-1-w { background-position: -64px -64px; }
.ui-icon-arrowreturn-1-n { background-position: -80px -64px; }
.ui-icon-arrowreturn-1-e { background-position: -96px -64px; }
.ui-icon-arrowreturn-1-s { background-position: -112px -64px; }
.ui-icon-arrowrefresh-1-w { background-position: -128px -64px; }
.ui-icon-arrowrefresh-1-n { background-position: -144px -64px; }
.ui-icon-arrowrefresh-1-e { background-position: -160px -64px; }
.ui-icon-arrowrefresh-1-s { background-position: -176px -64px; }
.ui-icon-arrow-4 { background-position: 0 -80px; }
.ui-icon-arrow-4-diag { background-position: -16px -80px; }
.ui-icon-extlink { background-position: -32px -80px; }
.ui-icon-newwin { background-position: -48px -80px; }
.ui-icon-refresh { background-position: -64px -80px; }
.ui-icon-shuffle { background-position: -80px -80px; }
.ui-icon-transfer-e-w { background-position: -96px -80px; }
.ui-icon-transferthick-e-w { background-position: -112px -80px; }
.ui-icon-folder-collapsed { background-position: 0 -96px; }
.ui-icon-folder-open { background-position: -16px -96px; }
.ui-icon-document { background-position: -32px -96px; }
.ui-icon-document-b { background-position: -48px -96px; }
.ui-icon-note { background-position: -64px -96px; }
.ui-icon-mail-closed { background-position: -80px -96px; }
.ui-icon-mail-open { background-position: -96px -96px; }
.ui-icon-suitcase { background-position: -112px -96px; }
.ui-icon-comment { background-position: -128px -96px; }
.ui-icon-person { background-position: -144px -96px; }
.ui-icon-print { background-position: -160px -96px; }
.ui-icon-trash { background-position: -176px -96px; }
.ui-icon-locked { background-position: -192px -96px; }
.ui-icon-unlocked { background-position: -208px -96px; }
.ui-icon-bookmark { background-position: -224px -96px; }
.ui-icon-tag { background-position: -240px -96px; }
.ui-icon-home { background-position: 0 -112px; }
.ui-icon-flag { background-position: -16px -112px; }
.ui-icon-calendar { background-position: -32px -112px; }
.ui-icon-cart { background-position: -48px -112px; }
.ui-icon-pencil { background-position: -64px -112px; }
.ui-icon-clock { background-position: -80px -112px; }
.ui-icon-disk { background-position: -96px -112px; }
.ui-icon-calculator { background-position: -112px -112px; }
.ui-icon-zoomin { background-position: -128px -112px; }
.ui-icon-zoomout { background-position: -144px -112px; }
.ui-icon-search { background-position: -160px -112px; }
.ui-icon-wrench { background-position: -176px -112px; }
.ui-icon-gear { background-position: -192px -112px; }
.ui-icon-heart { background-position: -208px -112px; }
.ui-icon-star { background-position: -224px -112px; }
.ui-icon-link { background-position: -240px -112px; }
.ui-icon-cancel { background-position: 0 -128px; }
.ui-icon-plus { background-position: -16px -128px; }
.ui-icon-plusthick { background-position: -32px -128px; }
.ui-icon-minus { background-position: -48px -128px; }
.ui-icon-minusthick { background-position: -64px -128px; }
.ui-icon-close { background-position: -80px -128px; }
.ui-icon-closethick { background-position: -96px -128px; }
.ui-icon-key { background-position: -112px -128px; }
.ui-icon-lightbulb { background-position: -128px -128px; }
.ui-icon-scissors { background-position: -144px -128px; }
.ui-icon-clipboard { background-position: -160px -128px; }
.ui-icon-copy { background-position: -176px -128px; }
.ui-icon-contact { background-position: -192px -128px; }
.ui-icon-image { background-position: -208px -128px; }
.ui-icon-video { background-position: -224px -128px; }
.ui-icon-script { background-position: -240px -128px; }
.ui-icon-alert { background-position: 0 -144px; }
.ui-icon-info { background-position: -16px -144px; }
.ui-icon-notice { background-position: -32px -144px; }
.ui-icon-help { background-position: -48px -144px; }
.ui-icon-check { background-position: -64px -144px; }
.ui-icon-bullet { background-position: -80px -144px; }
.ui-icon-radio-off { background-position: -96px -144px; }
.ui-icon-radio-on { background-position: -112px -144px; }
.ui-icon-pin-w { background-position: -128px -144px; }
.ui-icon-pin-s { background-position: -144px -144px; }
.ui-icon-play { background-position: 0 -160px; }
.ui-icon-pause { background-position: -16px -160px; }
.ui-icon-seek-next { background-position: -32px -160px; }
.ui-icon-seek-prev { background-position: -48px -160px; }
.ui-icon-seek-end { background-position: -64px -160px; }
.ui-icon-seek-first { background-position: -80px -160px; }
.ui-icon-stop { background-position: -96px -160px; }
.ui-icon-eject { background-position: -112px -160px; }
.ui-icon-volume-off { background-position: -128px -160px; }
.ui-icon-volume-on { background-position: -144px -160px; }
.ui-icon-power { background-position: 0 -176px; }
.ui-icon-signal-diag { background-position: -16px -176px; }
.ui-icon-signal { background-position: -32px -176px; }
.ui-icon-battery-0 { background-position: -48px -176px; }
.ui-icon-battery-1 { background-position: -64px -176px; }
.ui-icon-battery-2 { background-position: -80px -176px; }
.ui-icon-battery-3 { background-position: -96px -176px; }
.ui-icon-circle-plus { background-position: 0 -192px; }
.ui-icon-circle-minus { background-position: -16px -192px; }
.ui-icon-circle-close { background-position: -32px -192px; }
.ui-icon-circle-triangle-e { background-position: -48px -192px; }
.ui-icon-circle-triangle-s { background-position: -64px -192px; }
.ui-icon-circle-triangle-w { background-position: -80px -192px; }
.ui-icon-circle-triangle-n { background-position: -96px -192px; }
.ui-icon-circle-arrow-e { background-position: -112px -192px; }
.ui-icon-circle-arrow-s { background-position: -128px -192px; }
.ui-icon-circle-arrow-w { background-position: -144px -192px; }
.ui-icon-circle-arrow-n { background-position: -160px -192px; }
.ui-icon-circle-zoomin { background-position: -176px -192px; }
.ui-icon-circle-zoomout { background-position: -192px -192px; }
.ui-icon-circle-check { background-position: -208px -192px; }
.ui-icon-circlesmall-plus { background-position: 0 -208px; }
.ui-icon-circlesmall-minus { background-position: -16px -208px; }
.ui-icon-circlesmall-close { background-position: -32px -208px; }
.ui-icon-squaresmall-plus { background-position: -48px -208px; }
.ui-icon-squaresmall-minus { background-position: -64px -208px; }
.ui-icon-squaresmall-close { background-position: -80px -208px; }
.ui-icon-grip-dotted-vertical { background-position: 0 -224px; }
.ui-icon-grip-dotted-horizontal { background-position: -16px -224px; }
.ui-icon-grip-solid-vertical { background-position: -32px -224px; }
.ui-icon-grip-solid-horizontal { background-position: -48px -224px; }
.ui-icon-gripsmall-diagonal-se { background-position: -64px -224px; }
.ui-icon-grip-diagonal-se { background-position: -80px -224px; }
/* Misc visuals
/* Corner radius */
.ui-corner-tl { -moz-border-radius-topleft: 5px; -webkit-border-top-left-radius: 5px; }
.ui-corner-tr { -moz-border-radius-topright: 5px; -webkit-border-top-right-radius: 5px; }
.ui-corner-bl { -moz-border-radius-bottomleft: 5px; -webkit-border-bottom-left-radius: 5px; }
.ui-corner-br { -moz-border-radius-bottomright: 5px; -webkit-border-bottom-right-radius: 5px; }
.ui-corner-top { -moz-border-radius-topleft: 5px; -webkit-border-top-left-radius: 5px; -moz-border-radius-topright: 5px; -webkit-border-top-right-radius: 5px; }
.ui-corner-bottom { -moz-border-radius-bottomleft: 5px; -webkit-border-bottom-left-radius: 5px; -moz-border-radius-bottomright: 5px; -webkit-border-bottom-right-radius: 5px; }
.ui-corner-right { -moz-border-radius-topright: 5px; -webkit-border-top-right-radius: 5px; -moz-border-radius-bottomright: 5px; -webkit-border-bottom-right-radius: 5px; }
.ui-corner-left { -moz-border-radius-topleft: 5px; -webkit-border-top-left-radius: 5px; -moz-border-radius-bottomleft: 5px; -webkit-border-bottom-left-radius: 5px; }
.ui-corner-all { -moz-border-radius: 5px; -webkit-border-radius: 5px; }
/* Overlays */
.ui-widget-overlay { background: #aaaaaa url(images/ui-bg_flat_0_aaaaaa_40x100.png) 50% 50% repeat-x; opacity: .30;filter:Alpha(Opacity=30); }
.ui-widget-shadow { margin: -8px 0 0 -8px; padding: 8px; background: #aaaaaa url(images/ui-bg_flat_0_aaaaaa_40x100.png) 50% 50% repeat-x; opacity: .30;filter:Alpha(Opacity=30); -moz-border-radius: 8px; -webkit-border-radius: 8px; }/* Accordion
.ui-accordion .ui-accordion-header { cursor: pointer; position: relative; margin-top: 1px; zoom: 1; }
.ui-accordion .ui-accordion-li-fix { display: inline; }
.ui-accordion .ui-accordion-header-active { border-bottom: 0 !important; }
.ui-accordion .ui-accordion-header a { display: block; font-size: 1em; padding: .5em .5em .5em 2.2em; }
.ui-accordion .ui-accordion-header .ui-icon { position: absolute; left: .5em; top: 50%; margin-top: -8px; }
.ui-accordion .ui-accordion-content { padding: 1em 2.2em; border-top: 0; margin-top: -2px; position: relative; top: 1px; margin-bottom: 2px; overflow: auto; display: none; }
.ui-accordion .ui-accordion-content-active { display: block; }/* Datepicker
.ui-datepicker { width: 17em; padding: .2em .2em 0; }
.ui-datepicker .ui-datepicker-header { position:relative; padding:.2em 0; }
.ui-datepicker .ui-datepicker-prev, .ui-datepicker .ui-datepicker-next { position:absolute; top: 2px; width: 1.8em; height: 1.8em; }
.ui-datepicker .ui-datepicker-prev-hover, .ui-datepicker .ui-datepicker-next-hover { top: 1px; }
.ui-datepicker .ui-datepicker-prev { left:2px; }
.ui-datepicker .ui-datepicker-next { right:2px; }
.ui-datepicker .ui-datepicker-prev-hover { left:1px; }
.ui-datepicker .ui-datepicker-next-hover { right:1px; }
.ui-datepicker .ui-datepicker-prev span, .ui-datepicker .ui-datepicker-next span { display: block; position: absolute; left: 50%; margin-left: -8px; top: 50%; margin-top: -8px; }
.ui-datepicker .ui-datepicker-title { margin: 0 2.3em; line-height: 1.8em; text-align: center; }
.ui-datepicker .ui-datepicker-title select { float:left; font-size:1em; margin:1px 0; }
.ui-datepicker select.ui-datepicker-month-year {width: 100%;}
.ui-datepicker select.ui-datepicker-month,
.ui-datepicker select.ui-datepicker-year { width: 49%;}
.ui-datepicker .ui-datepicker-title select.ui-datepicker-year { float: right; }
.ui-datepicker table {width: 100%; font-size: .9em; border-collapse: collapse; margin:0 0 .4em; }
.ui-datepicker th { padding: .7em .3em; text-align: center; font-weight: bold; border: 0; }
.ui-datepicker td { border: 0; padding: 1px; }
.ui-datepicker td span, .ui-datepicker td a { display: block; padding: .2em; text-align: right; text-decoration: none; }
.ui-datepicker .ui-datepicker-buttonpane { background-image: none; margin: .7em 0 0 0; padding:0 .2em; border-left: 0; border-right: 0; border-bottom: 0; }
.ui-datepicker .ui-datepicker-buttonpane button { float: right; margin: .5em .2em .4em; cursor: pointer; padding: .2em .6em .3em .6em; width:auto; overflow:visible; }
.ui-datepicker .ui-datepicker-buttonpane button.ui-datepicker-current { float:left; }
/* with multiple calendars */
.ui-datepicker.ui-datepicker-multi { width:auto; }
.ui-datepicker-multi .ui-datepicker-group { float:left; }
.ui-datepicker-multi .ui-datepicker-group table { width:95%; margin:0 auto .4em; }
.ui-datepicker-multi-2 .ui-datepicker-group { width:50%; }
.ui-datepicker-multi-3 .ui-datepicker-group { width:33.3%; }
.ui-datepicker-multi-4 .ui-datepicker-group { width:25%; }
.ui-datepicker-multi .ui-datepicker-group-last .ui-datepicker-header { border-left-width:0; }
.ui-datepicker-multi .ui-datepicker-group-middle .ui-datepicker-header { border-left-width:0; }
.ui-datepicker-multi .ui-datepicker-buttonpane { clear:left; }
.ui-datepicker-row-break { clear:both; width:100%; }
/* RTL support */
.ui-datepicker-rtl { direction: rtl; }
.ui-datepicker-rtl .ui-datepicker-prev { right: 2px; left: auto; }
.ui-datepicker-rtl .ui-datepicker-next { left: 2px; right: auto; }
.ui-datepicker-rtl .ui-datepicker-prev:hover { right: 1px; left: auto; }
.ui-datepicker-rtl .ui-datepicker-next:hover { left: 1px; right: auto; }
.ui-datepicker-rtl .ui-datepicker-buttonpane { clear:right; }
.ui-datepicker-rtl .ui-datepicker-buttonpane button { float: left; }
.ui-datepicker-rtl .ui-datepicker-buttonpane button.ui-datepicker-current { float:right; }
.ui-datepicker-rtl .ui-datepicker-group { float:right; }
.ui-datepicker-rtl .ui-datepicker-group-last .ui-datepicker-header { border-right-width:0; border-left-width:1px; }
.ui-datepicker-rtl .ui-datepicker-group-middle .ui-datepicker-header { border-right-width:0; border-left-width:1px; }
/* IE6 IFRAME FIX (taken from datepicker 1.5.3 */
.ui-datepicker-cover {
display: none; /*sorry for IE5*/
display/**/: block; /*sorry for IE5*/
position: absolute; /*must have*/
z-index: -1; /*must have*/
filter: mask(); /*must have*/
top: -4px; /*must have*/
left: -4px; /*must have*/
width: 200px; /*must have*/
height: 200px; /*must have*/
}/* Dialog
.ui-dialog { position: relative; padding: .2em; width: 300px; }
.ui-dialog .ui-dialog-titlebar { padding: .5em .3em .3em 1em; position: relative; }
.ui-dialog .ui-dialog-title { float: left; margin: .1em 0 .2em; }
.ui-dialog .ui-dialog-titlebar-close { position: absolute; right: .3em; top: 50%; width: 19px; margin: -10px 0 0 0; padding: 1px; height: 18px; }
.ui-dialog .ui-dialog-titlebar-close span { display: block; margin: 1px; }
.ui-dialog .ui-dialog-titlebar-close:hover, .ui-dialog .ui-dialog-titlebar-close:focus { padding: 0; }
.ui-dialog .ui-dialog-content { border: 0; padding: .5em 1em; background: none; overflow: auto; zoom: 1; }
.ui-dialog .ui-dialog-buttonpane { text-align: left; border-width: 1px 0 0 0; background-image: none; margin: .5em 0 0 0; padding: .3em 1em .5em .4em; }
.ui-dialog .ui-dialog-buttonpane button { float: right; margin: .5em .4em .5em 0; cursor: pointer; padding: .2em .6em .3em .6em; line-height: 1.4em; width:auto; overflow:visible; }
.ui-dialog .ui-resizable-se { width: 14px; height: 14px; right: 3px; bottom: 3px; }
.ui-draggable .ui-dialog-titlebar { cursor: move; }
/* Progressbar
.ui-progressbar { height:2em; text-align: left; }
.ui-progressbar .ui-progressbar-value {margin: -1px; height:100%; }/* Resizable
.ui-resizable { position: relative;}
.ui-resizable-handle { position: absolute;font-size: 0.1px;z-index: 99999; display: block;}
.ui-resizable-disabled .ui-resizable-handle, .ui-resizable-autohide .ui-resizable-handle { display: none; }
.ui-resizable-n { cursor: n-resize; height: 7px; width: 100%; top: -5px; left: 0px; }
.ui-resizable-s { cursor: s-resize; height: 7px; width: 100%; bottom: -5px; left: 0px; }
.ui-resizable-e { cursor: e-resize; width: 7px; right: -5px; top: 0px; height: 100%; }
.ui-resizable-w { cursor: w-resize; width: 7px; left: -5px; top: 0px; height: 100%; }
.ui-resizable-se { cursor: se-resize; width: 12px; height: 12px; right: 1px; bottom: 1px; }
.ui-resizable-sw { cursor: sw-resize; width: 9px; height: 9px; left: -5px; bottom: -5px; }
.ui-resizable-nw { cursor: nw-resize; width: 9px; height: 9px; left: -5px; top: -5px; }
.ui-resizable-ne { cursor: ne-resize; width: 9px; height: 9px; right: -5px; top: -5px;}/* Slider
.ui-slider { position: relative; text-align: left; }
.ui-slider .ui-slider-handle { position: absolute; z-index: 2; width: 1.2em; height: 1.2em; cursor: default; }
.ui-slider .ui-slider-range { position: absolute; z-index: 1; font-size: .7em; display: block; border: 0; }
.ui-slider-horizontal { height: .8em; }
.ui-slider-horizontal .ui-slider-handle { top: -.3em; margin-left: -.6em; }
.ui-slider-horizontal .ui-slider-range { top: 0; height: 100%; }
.ui-slider-horizontal .ui-slider-range-min { left: 0; }
.ui-slider-horizontal .ui-slider-range-max { right: 0; }
.ui-slider-vertical { width: .8em; height: 100px; }
.ui-slider-vertical .ui-slider-handle { left: -.3em; margin-left: 0; margin-bottom: -.6em; }
.ui-slider-vertical .ui-slider-range { left: 0; width: 100%; }
.ui-slider-vertical .ui-slider-range-min { bottom: 0; }
.ui-slider-vertical .ui-slider-range-max { top: 0; }/* Tabs
.ui-tabs { padding: .2em; zoom: 1; }
.ui-tabs .ui-tabs-nav { list-style: none; position: relative; padding: .2em .2em 0; }
.ui-tabs .ui-tabs-nav li { position: relative; float: left; border-bottom-width: 0 !important; margin: 0 .2em -1px 0; padding: 0; }
.ui-tabs .ui-tabs-nav li a { float: left; text-decoration: none; padding: .5em 1em; }
.ui-tabs .ui-tabs-nav li.ui-tabs-selected { padding-bottom: 1px; border-bottom-width: 0; }
.ui-tabs .ui-tabs-nav li.ui-tabs-selected a, .ui-tabs .ui-tabs-nav li.ui-state-disabled a, .ui-tabs .ui-tabs-nav li.ui-state-processing a { cursor: text; }
.ui-tabs .ui-tabs-nav li a, .ui-tabs.ui-tabs-collapsible .ui-tabs-nav li.ui-tabs-selected a { cursor: pointer; } /* first selector in group seems obsolete, but required to overcome bug in Opera applying cursor: text overall if defined elsewhere... */
.ui-tabs .ui-tabs-panel { padding: 1em 1.4em; display: block; border-width: 0; background: none; }
.ui-tabs .ui-tabs-hide { display: none !important; }
</style>
<script type="text/javascript" src="#WORKSPACE_IMAGES#jquery.js"></script>
<script type="text/javascript" src="#WORKSPACE_IMAGES#jquery-ui.js"></script>
#HEAD#
</head>
<body #ONLOAD#>#FORM_OPEN# -
Migrating old account to new Macbook Pro
I got a nice new Macbook Pro (2010 version) with the i7 processor. I had to get a new cable to migrate my information from my old Macbook Pro (2006?)so I performed the migration the next day. The computer ran fine for several days until I rebooted it. All I got was part way through the boot and gray shadowing came down the screen and the message to force shut down the computer came up.
The computer could boot into safe mode. Tried to reinstall the system with no luck. Hardware test showed the computer was fine. Started in verbose mode <command-v>, which seemed to show that "com.bresink.driver.BRESINKx86Monitoring(3.0) was the culprit.
I found that in /Library/StartupItems and removed it. Computer started fine!
I think that file is associated with the iStat widget and is not compatible with the new processors. I hope this post saves someone else all the worry that I went throughThat file has nothing to do with iStat Pro — it's part of Marcel Bresink's *Hardware Monitor* utility. I suspect you probably had an outdated version of it that was incompatible with your new machine or its OS.
-
Migration from G4 Powerbook(partitioned) to new IMAC
I am tried to use Migration today, from G4 Titanium DVI Powerbook(partitioned) #1 MacTiger 10.4.11- 14GB, #2 OSX 9.9GB, #3 OS9 4GB to my new IMAC that I have had for a couple of weeks. When I had to enter the name info, it kept on telling me that I had to change the names as they were already existing. Began migration and it ran for 3 hours or more then stopped with 2 hours 58 minutes remaining on the clock. I let it go for over another hour. Nothing happening. Tried to cancel but 3 new icons were on my IMAC desktop. Rainbow wheel goes round and round etc. on IMAC. I then held down the power button on the G4 to power off. The 3 new icons on my IMAC desktop, I dragged them to the trash. I'm all in a sweat just writing this down. Who would like to hold my hand as I walk through the valley of the shadow........
Thanks for your reading, responding, succeeding. You guys always come through. Are PC people this fortunate?I'm not sure what you are asking. Yes you can change the name of a user account, but it's a bit complicated. It would be easier to simply transfer the files as I've outlined rather than trying to use Migration Assistant which will attempt to transfer everything in the user account, which is ill-advised. There are PPC components in your old system that you do not want moved to the new computer. PPC components can gum up the works on an Intel system.
Migration Assistant is an excellent tool but it's not the right tool when you are migrating from a PPC Mac to an Intel one. See the following:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior 4.1, TechTool Pro 4.6.1, SuperDuper 2.5, and Drive Genius 2.0.2 work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode or copying the critical contents to CD and DVD or an external hard drive will work better when moving from PowerPC to Intel Macs.
Basically the instructions you should follow are:
1. Backup your data first. This is vitally important in case you make a mistake or there's some other problem.
2. Connect a Firewire cable between your old Mac and your new Intel Mac.
3. Startup your old Mac in Target Disk Mode.
4. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
4. Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/ (copy the whole folder)
/Home /Library/Calendars (copy the whole folder)
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to Macjack for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.
Revised 3/12/2008
Maybe you are looking for
-
UWL task takes up to 2 minutes to appear
Hi there, We have a situation where the UWL task takes between 1 minute and 2 minuts to appear in the user's inbox. in our analysis we have found that the task is created immediatly in the business process but it set with an inactive status. After a
-
I am trying to figure out how to drill down from a dimension heirarchy to a fact detail. It just does seem to work. I have Manager ---Project manager Then projects facts The totals by project manager work well, but I tried creating another level belo
-
Is there a different between Photoshop 6 for MAC or PC.
i am searching after an old "Photoshop Element 6.0" for an old MAC Ibook PC G3. Is there a different betwenn the Version for PC and MAC?
-
Wired Mighty Mouse vs. Wireless Mighty Mouse
Hey, my wired Mighty Mouse track ball just crapped out on me (I can't scroll down anymore) so I guess I am looking to buy another one. Does anyone have any experience and/or opinions on the Wireless Mighty Mouse track balls being any more reliable or
-
feeling pretty foolish and frustrated at the moment. In CF Builder 2 I started a new project and placed it in a new directory under wwwroot. A very simple hello world html file will run in Builder's preview but not in a browser. Another very simple c