Migrating wiki from Leopard Server (10.5) to Lion Server

Is there any way to migrate Wiki Server data from Leopard Server (i.e. 10.5 not 10.6) to Lion Server without upgrading to Snow Leopard first. I'm happy to set up everything else afresh but I've migrated wiki data before and it was a nightmare.
The situation we'll soon be in is needing to migrate wiki data on a PowerPC mac running Leopard Server to a new Power Mac pre-installed with Lion Server.

From: http://images.apple.com/macosx/server/docs/Upgrading_and_Migrating_v10.7.pdf
Need to set up Lion Server first, then:
Copy the wiki data located in /Library/Collaboration/ by default or in the location specified in Server Admin on the v10.5.8 or later server to a local volume Lion Server can access.
Use the following steps to manually migrate your Mac OS X v10.5.8 or later server’s Wiki data to Lion Server.
If you are migrating a v10.5.8 wiki server’s data, make sure Lion Server is bound to the same Open Directory master as the v10.5.8 server, so the ACLs for wikis can convert. If not, wikis are only readable or writeable by admins, and ACLs must be reset.
To migrate wiki data:
1 Start Wiki service in the Server app.
2 Enter the following command.
sudo wikiadmin migrate -r /path/to/collaboration/folder

Similar Messages

How can i remove old wikis from Leopard Server in Lion?.

Hello all,
I just update to Lion, and now I can´t access to delete them.

I decided to temporarily assign administrator permissions on the server to a user of the wiki, that way I was able to delete some of the wikis. Best Regards.

Migrate wiki from MLS to MAVS

Dear Folks,
I want to provide a solution on how to migrate the Wiki from a Mountain Lion Server to a Mavericks Server. Both Servers are running but in different locations and they can't communicate directly with each other. Upgrading the MLS was no option - after what I had read in hundreds of threads. The MLS is a 10.8.5 (with the latest version of server.app up until the 15th of October 2013) and Mavericks a 10.9.1 (with the latest version of server.app up until New Years Eve).
I hadn't done it without the help of Andreas from Metalab in Vienna (lovely Hackspace) - so the grace goes to him!!
First things first - he isolated 2 issues on MLS - revolving postgresql Version AND Socket! Thank you Apple-developers you did a great job here - since this product is called „The Server for everyone“ I believe either the title is incorrect or some guys haven’t understood what the a server for everyone implies - since everyone isn’t a geek, nerd, developer etc. - think about it!
Trying to connect to psql on MLS:
bash-3.2# psql
psql: could not connect to server: No such file or directory
          Is the server running locally and accepting
          connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
What?!
bash-3.2# serveradmin status postgres
postgres:state = "RUNNING"
What?!
So he started digging on MLS:
bash-3.2# netstat -na|grep LISTEN
nothing tangible here - nothing ist listening to 5432
Dig deeper on MLS:
bash-3.2# lsof | grep postgre
          #output omitted for clarity
postgres_ 2546      _postgres   10u     unix 0xa319efaa0af41357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
postgres_ 2547      _postgres   10u     unix 0xa319efaa0af3fbe7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 2548      _postgres   10u     unix 0xa319efaa0af3fa57       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 2549      _postgres   10u     unix 0xa319efaa0af3f8c7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 3102      _postgres   10u     unix 0xa319efaa0b220357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
Hold the horses still - that got him thinking! How does that fit to the output of the psql-command just seconds earlier (and I literally mean seconds!) Can you see it?
The truth is, the Socket is at:
/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
but is expected by psql to be in /var/psql_socket/.s.PGSQL.5432!
Expected What?!
Verified it again on MLS:
bash-3.2# psql
psql: could not connect to server: No such file or directory
          Is the server running locally and accepting
          connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
bash-3.2# psql --help
Yep - when postgresql was compiled obviously somebody was sitting on his fingers - during implementation nobody had told psql the path for the socket at the "new" location?! Ergo - psql is looking for the socket in the default location - where it is not.
Then, with the help, he managed it to get in.
Trying to get in on MLS:
bash-3.2# psql -p "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
psql: invalid port number: "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
Trying again on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
psql: could not connect to server: Not a directory
          Is the server running locally and accepting
          connections on Unix domain socket "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432/.s.PGSQL.5432"?
And again - almost there on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432
psql: FATAL: role "root" does not exist
Typo:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -u colab
psql: invalid option -- u
Try "psql --help" for more information.
And - tata - he was in on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 template1 collab
psql (9.1.9, server 9.2.4)
WARNING: psql version 9.1, server version 9.2.
         Some psql features might not work.
Type "help" for help.
template1=#
Lets find the databases and roles on MLS:
template1=# \l
                                   List of databases
       Name        |   Owner    | Encoding | Collate | Ctype |    Access privileges
-------------------+------------+----------+---------+-------+------------------ -------
caldav            | caldav     | UTF8     | C       | C     |
collab            | collab     | UTF8     | C       | C     |
device_management | _devicemgr | UTF8     | C       | C     |
postgres          | _postgres | UTF8     | C       | C     |
template0         | _postgres | UTF8     | C       | C     | =c/_postgres           +
                   |            |          |         |       | _postgres=CTc/_postgres
template1         | _postgres | UTF8     | C       | C     | _postgres=CTc/_postgres+
                   |            |          |         |       | =c/_postgres
webauth           | webauth    | UTF8     | C       | C     |
(7 rows)
And there are the roles on MLS:
template1=# \du
                              List of roles
Role name |                   Attributes                   | Member of
------------+------------------------------------------------+-----------
_devicemgr | Create DB                                      | {}
_postgres | Superuser, Create role, Create DB, Replication | {}
caldav     | Create DB                                      | {}
collab     | Superuser, Create role, Create DB              | {}
webauth    | Superuser, Create role, Create DB              | {}
Aaaaah - so there is a role collab and a database collab! Lets connect to the "right" database and dive into it on MLS.
template1=# \q
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 collab collab
psql (9.1.9, server 9.2.4)
WARNING: psql version 9.1, server version 9.2.
         Some psql features might not work.
Type "help" for help.
collab=# \d
                   List of relations
Schema |            Name             | Type | Owner
--------+-----------------------------+-------+--------
public | blog_entity                 | table | collab
public | document_entity             | table | collab
public | entity                      | table | collab
public | entity_acls                 | table | collab
public | entity_acls_defaults        | table | collab
public | entity_attrs                | table | collab
public | entity_changesets           | table | collab
public | entity_comment              | table | collab
public | entity_lock                 | table | collab
public | entity_preview              | table | collab
public | entity_private_attrs        | table | collab
public | entity_tag                  | table | collab
public | entity_type                 | table | collab
public | file_entity                 | table | collab
public | filedata_entity             | table | collab
public | filename_reservation        | table | collab
public | global_settings             | table | collab
public | groups                      | table | collab
public | migration_entity            | table | collab
public | migration_status            | table | collab
public | migrationplaceholder_entity | table | collab
public | notification                | table | collab
public | page_entity                 | table | collab
public | podcast_entity              | table | collab
public | podcast_episode_entity      | table | collab
public | preview_queue               | table | collab
public | project_entity              | table | collab
public | relationship                | table | collab
public | savedquery_entity           | table | collab
public | search_index                | table | collab
public | search_stat                 | table | collab
public | session                     | table | collab
public | subscription                | table | collab
public | user_activity               | table | collab
public | user_entity                 | table | collab
public | user_entity_favorites       | table | collab
public | user_entity_read_status     | table | collab
public | user_entity_unread_status   | table | collab
public | user_entity_updates         | table | collab
public | user_entity_watched         | table | collab
public | user_readall_time           | table | collab
(41 rows)
That looks fantastic! Lets start dumping with some help through pg_dump --help and then issuing the following on MLS:
bash-3.2# pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
pg_dump: server version: 9.2.4; pg_dump version: 9.1.9
pg_dump: aborting because of server version mismatch
What?! How could that be?! The commands refer to an older version?!
Start digging again on MLS!
bash-3.2# which psql
/usr/bin/psql
bash-3.2# which pg_dump
/usr/bin/pg_dump
That's where I stepped in and told Andreas "Hey - ahm - I know of a path completely different…. /Applications/Server.app/.….". Thanks mate!
Dig again on MLS!
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump --version
pg_dump (PostgreSQL) 9.2.4
Lovely - that one looks good - lets use it. All of that got us finally to the right command on MLS.
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
There it is - the whole Database on the stick - finally - it took Andreas only 5 Minutes - approximately? I am just baffled.
Then I copied the Folders from the /Library/Server/Wiki/FileData of the MLS to the exact same location on the MAVS and sat permission - navigating to /Library/Server/Wiki first:
bash-3.2# chown -R _teamsserver:_teamsserver FileData/
bash-3.2# chmod -R +a "_www allow read" FileData/
I compared the the collab DB on the MLS with the MAVS collab DB to see the differences - BTW - the Socket has moved again on the MLS! Move up in this documentary and you’ll see on how to find it on MAVS.
bash-3.2# lsof | grep 5432
          #output omitted for clarity
postgres_   382    _teamsserver    3u     unix 0x399cdd6eeea1efe1       0t0         /Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432
          #output omitted for clarity
bash-3.2# psql -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 collab collab
psql (9.2.4)
Type "help" for help.
collab=# \d
                   List of relations
Schema |            Name             | Type | Owner
--------+-----------------------------+-------+--------
public | adc_device_entity           | table | collab
public | adc_team_entity             | table | collab
public | blog_entity                 | table | collab
public | bot_entity                  | table | collab
public | botgroup_entity             | table | collab
public | botrun_entity               | table | collab
public | build_agent_registry        | table | collab
public | document_entity             | table | collab
public | email_notification          | table | collab
public | entity                      | table | collab
public | entity_acls                 | table | collab
public | entity_acls_defaults        | table | collab
public | entity_attrs                | table | collab
public | entity_auditlog             | table | collab
public | entity_changesets           | table | collab
public | entity_comment              | table | collab
public | entity_lock                 | table | collab
public | entity_preview              | table | collab
public | entity_private_attrs        | table | collab
public | entity_tag                  | table | collab
public | entity_type                 | table | collab
public | file_entity                 | table | collab
public | filedata_entity             | table | collab
public | filename_reservation        | table | collab
public | global_settings             | table | collab
public | groups                      | table | collab
public | migration_entity            | table | collab
public | migration_status            | table | collab
public | migrationplaceholder_entity | table | collab
public | page_entity                 | table | collab
public | podcast_entity              | table | collab
public | podcast_episode_entity      | table | collab
public | preview_queue               | table | collab
public | relationship                | table | collab
public | savedquery_entity           | table | collab
public | scm_commit_entity           | table | collab
public | scm_server                  | table | collab
public | scmrepogroup_entity         | table | collab
public | search_index                | table | collab
public | search_stat                 | table | collab
public | session                     | table | collab
public | subscription                | table | collab
public | timeseries                  | table | collab
public | timeseries_toc              | table | collab
public | user_activity               | table | collab
public | user_entity                 | table | collab
public | user_entity_favorites       | table | collab
public | user_entity_read_status     | table | collab
public | user_entity_unread_status   | table | collab
public | user_entity_updates         | table | collab
public | user_entity_watched         | table | collab
public | user_readall_time           | table | collab
public | visible_entity_tag          | view | collab
public | wiki_entity                 | table | collab
public | work_queue                  | table | collab
public | work_schedule               | table | collab
public | work_schedule_recurrence    | table | collab
public | work_schedule_status        | table | collab
(58 rows)
Hmmm - 41 tables in the old, and 58 in the new. What am I going to do? To be able to roll back I dumped the MAVS DB before I would do anything else.
I had to decide between trying to take the old MLS DB and just pg_restore it into the MAVS DB, or - trying to upgrade the MLS instance to MAVS. I was afraid doing the upgrade since the MLS was a mess. At the end I would decide to go for the latter - since I had dumps. It took a while but - hey - it worked. Everything in place! Wiki running - everything else, too! The database has now 58 tables - ok - lets dump it. Notice again - no need to specify the proper version of pg_dump, but the Socket has changed from MLS to MAVS - again - you could see this when I connected with psql as well!
Please use (-F c) compression when dumping - otherwise you’ll receive a nasty error when importing it at the MAVS.
bash-3.2# pg_dump -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 -F c -f /Volumes/USBSTICK/MLSafterupgrade2MAVS_collab_db_compressed.pgdump -U collab collab
I then copied the dump to the server - the Desktop of the administrativ account - I did it through screensharing which is accessible after establishing a VPN to the location the server resides in.
Unfortunately the command for pg_restore has a different syntax then the pg_dump. Use pg_dump --help to see the details. I’ll explain it quickly:
-c is to clean entries in the target tables (you must not use capital c)
-d specifies the database into which you would like to restore
-h specifies (again) where the DB is - the socket
-p the port to use
-U is the role that likes to work on the DB
you must not use -f since it’s not needed
bash-3.2# pg_restore -c -d collab -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 /Volumes/OSXDATA/Users/macminiadmin/Desktop/MLScollabdb_compressed.pgdump -U collab
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2466; 2605 16639 CAST CAST (text[] AS public.hstore)
pg_restore: [archiver (db)] could not execute query: ERROR: cannot drop cast from text[] to public.hstore because extension hstore requires it
HINT: You can drop extension hstore instead.
    Command was: DROP CAST (text[] AS public.hstore);
pg_restore: [archiver (db)] Error from TOC entry 1816; 2616 16636 OPERATOR CLASS hash_hstore_ops collab
pg_restore: [archiver (db)] could not execute query: ERROR: cannot drop operator class hash_hstore_ops for access method hash because extension hstore requires it
HINT: You can drop extension hstore instead.
    Command was: DROP OPERATOR CLASS public.hash_hstore_ops USING hash;
          #output omitted for clarity
I saw quite a lot errors (some revolving functions etc.) - however, it worked. Wikis are present again on the MAVS. Not without the initial help of Andreas - thank you once again!
I would like to recommend to everyone joining hackerspaces in their location. I do not know them in other areas - I can only speak for the metalab in Vienna. Fantastic place with fantastic, very knowledgable people. I would also recommend reading a book like PostgreSQL 9 Admin Cookbook - this helped me quit a lot as well. It’s available through various stores - virtual or real - choose what you prefer.

Frustrated, not angry...
Well folks. I think this is goodbye to OS X Server - the server that I thought was much easier to use. I've followed instructions on this forum and several others over the past 7 months. It's cost me so much time and headache.
Migrating wikis from Mountain Lion Server to Mavericks server has yet to work
Upgrading our Mountain Lion Server to Mavericks leaves us without wiki, calendar, and other services
Apple support docs don't do the trick
Phone calls with Apple support techs haven't provided any solutions.
Our current Mountain Lion Server suddenly lost all filesharing authentication capability and Apple enterprise solutions haven't been able to figure this one out.
I'm stuck with a server with broken mountain lion server I have never been able to upgrade and/or migrate and ultimately would be left to copy/paste wikis to a fresh Mavericks server, export/import calendars from each client station, and contacts - I don't even know how that's going to work.
I believe in keeping IT folks employed, but...
The support from Apple seems so marginal (just for the server) and the plethora of problems with upgrading to Mavericks server and/or the manual fight to only potentially get it done seems very un-Apple like and just downright counter to what Apple represents.
So I'll think different...
Our server will be relegated to a client machine with simple file sharing. Perhaps We'll buy Daylite to assume some of the responsibilites. Truth is, even when things were working, it was always flaky in some way.
I really wanted to employ OS X Server in an efficient way, but it's been more trouble than I can accomodate.
Fortunately I am not an average client user nor a novice, so working in terminal is comfortable.
Perhaps in a few years or so, I'll reconsider, but my experience with OS X server on Mountain Lion and Mavericks has affected my trust.
Thanks for all of the help to those who provided instructions, workarounds, directions toward solutions, etc.
For those of you who had a successful migration - consider yourself lucky.
...by the way...after finishing the incredible instructions on this page (and i sincerely mean that despite them not working for me) the result was a wiki page that looked like this
Caught exception "[<CSEntityPlaceholder 0x7fb2d15d5910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key externalID." [NSUnknownKeyException] executing route /app-context/wiki/:
0   CoreFoundation                      0x00007fff8a0fe25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff8da20e75 objc_exception_throw + 43
2   CSService                           0x0000000104bc7957 -[CSLocalServiceProxy forwardInvocation:] + 1229
3   CoreFoundation                      0x00007fff8a05c1c4 ___forwarding___ + 452
4   CoreFoundation                      0x00007fff8a05bf78 _CF_forwarding_prep_0 + 120
5   CSService                           0x0000000104bf9573 __27-[CSAppContextService init]_block_invoke240 + 180
6   CSService                           0x0000000104bdf81a __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
7   CSService                           0x0000000104be2d6c -[CSHTTPBackgroundResponse bounce:] + 286
8   Foundation                          0x00007fff9073976b __NSThread__main__ + 1318
9   libsystem_pthread.dylib             0x00007fff8bc58899 _pthread_body + 138
10 libsystem_pthread.dylib             0x00007fff8bc5872a _pthread_struct_init + 0
11 libsystem_pthread.dylib             0x00007fff8bc5cfc9 thread_start + 13

Please help, after migrating to snow leopard Server my VPN is not working

Hi,
After migrated to Snow Leopard Server, my VPN settings are not working, My users not able to connect to VPN.
Please find below log. Please let me know the solution for it.
2010-01-05 13:19:32 IST Incoming call... Address given to client = 192.168.1.72
Tue Jan 5 13:19:33 2010 : Directory Services Authentication plugin initialized
Tue Jan 5 13:19:33 2010 : Directory Services Authorization plugin initialized
Tue Jan 5 13:19:33 2010 : PPTP incoming call in progress from '95.222.205.164'...
Tue Jan 5 13:19:33 2010 : PPTP connection established.
Tue Jan 5 13:19:33 2010 : using link 0
Tue Jan 5 13:19:33 2010 : Using interface ppp0
Tue Jan 5 13:19:33 2010 : Connect: ppp0 <--> socket[34:17]
Tue Jan 5 13:19:33 2010 : sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x2794ebf2> <pcomp> <accomp>]
Tue Jan 5 13:19:34 2010 : rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x29205274> <pcomp> <accomp>]
Tue Jan 5 13:19:34 2010 : lcp_reqci: returning CONFACK.
Tue Jan 5 13:19:34 2010 : sent [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x29205274> <pcomp> <accomp>]
Tue Jan 5 13:19:36 2010 : sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x2794ebf2> <pcomp> <accomp>]
Tue Jan 5 13:19:36 2010 : rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <auth chap MS-v2> <magic 0x2794ebf2> <pcomp> <accomp>]
Tue Jan 5 13:19:36 2010 : sent [LCP EchoReq id=0x0 magic=0x2794ebf2]
Tue Jan 5 13:19:36 2010 : sent [CHAP Challenge id=0x8d <620015595e4967664c1310241b4b3254>, name = "nova.thecoverstory.com"]
Tue Jan 5 13:19:36 2010 : rcvd [LCP EchoReq id=0x0 magic=0x29205274]
Tue Jan 5 13:19:36 2010 : sent [LCP EchoRep id=0x0 magic=0x2794ebf2]
Tue Jan 5 13:19:36 2010 : rcvd [LCP EchoRep id=0x0 magic=0x29205274]
Tue Jan 5 13:19:39 2010 : sent [CHAP Challenge id=0x8d <620015595e4967664c1310241b4b3254>, name = "nova.thecoverstory.com"]
Tue Jan 5 13:19:40 2010 : rcvd [CHAP Response id=0x8d <c68742dc9457be5a61e444f00f53371d000000000000000044c6f89fa49ed8bf4c17a2861a2cfd 04ae1e6b9199527f9f00>, name = "jenny"]
Tue Jan 5 13:19:40 2010 : DSAuth plugin: Error -25300 while retrieving key agent password from the system keychain.
Tue Jan 5 13:19:40 2010 : DSAuth plugin: Could not retrieve key agent account information.
Tue Jan 5 13:19:40 2010 : sent [CHAP Success id=0x8d "S=B503F226B4DE4105A4711C0EA2E7C21B1A9A935D M=Access granted"]
Tue Jan 5 13:19:40 2010 : CHAP peer authentication succeeded for jenny
Tue Jan 5 13:19:40 2010 : DSAccessControl plugin: User 'jenny' authorized for access
Tue Jan 5 13:19:40 2010 : MPPE required, but keys are not available. Possible plugin problem?
Tue Jan 5 13:19:40 2010 : sent [LCP TermReq id=0x2 "MPPE required but not available"]
Tue Jan 5 13:19:40 2010 : Connection terminated.
Tue Jan 5 13:19:40 2010 : Connect time 0.2 minutes.
Tue Jan 5 13:19:40 2010 : Sent 0 bytes, received 0 bytes.
Tue Jan 5 13:19:40 2010 : PPTP disconnecting...
Tue Jan 5 13:19:40 2010 : PPTP disconnected
2010-01-05 13:19:40 IST --> Client with address = 192.168.1.72 has hungup
Thanks,
Gulab Pasha

Great !! save my trouble too
thanks a lot for the tip.

How can I migrate data from SQL Server 6,5 to Oracle 8?

We have a web site based on Microsoft SQL Server 6.5.Now we plan
to migrate the database to Oracle 8.
We have redesigned the tables structure and created tables under
Oracle 8, so we only need to migrate data from SQL Server.
We've exported data from SQL Server to text files.
How can we import data from files and restore to Oracle tables.
Is there a solution which let us to import data for particular
table columns,not all columns?
We'll be appreciated if somene can give suggestions.
Regards
Michael
null

Thank you for your reply.
I'll try the Oracle sqlloader utility first.
Regards
Micahel
Oracle Migration Workbench Team wrote:
: Michael,
: Oracle sqlloader is user for this sort of operation, see
: Oracle8i Utilities
: Release 8.1.5
: A67792-01
: available online through Oracle Technology Network.
: The Oracle Migration Workbench can be used to create bcp and
: sqlloader scripts, though since you have altered the schema
these
: scripts would need to be altered by hand after generation.
: Some thought has been put into redesigning table structures in
: the Oracle Migration Workbench, but currently it looks like
this
: reengineering will be left to be done by other tools, eg
Oracle
: Designer, once the SQLServer database has been duplicated with
as
: little change as possible onto Oracle.
: Hope that helps,
: Turloch
: Oracle Migration Workbench Team
: Michael (guest) wrote:
: : We have a web site based on Microsoft SQL Server 6.5.Now we
: plan
: : to migrate the database to Oracle 8.
: : We have redesigned the tables structure and created tables
: under
: : Oracle 8, so we only need to migrate data from SQL Server.
: : We've exported data from SQL Server to text files.
: : How can we import data from files and restore to Oracle
tables.
: : Is there a solution which let us to import data for
particular
: : table columns,not all columns?
: : We'll be appreciated if somene can give suggestions.
: : Regards
: : Michael
: Oracle Technology Network
: http://technet.oracle.com
null

Faster way to migrate data from SQL Server to Oracle 10g

We have to migrate data from SQL Server to Oracle 10 g.
One particular table on SQL Server has records around 1.25 millions.
We tried moving data using DTS package, but looks it will take hours with current speed of 300 records/minute.
This table has TEXT column, which has XML strings stored. I am not sure, if this is the reason for slow migration.
Would you please suggest better options to migrate it faster?
Thanks in advance !!!

Have you tried Migration work bench?

Migrate tracks from one server to another

Hello, I've read a few guides how to migrate tracks from one server to another, but it doesn't help me.
What I've done:
1) I've exported my SC from SLD at my old server
2) Then imported it at my new server
3) Updated CMS from SLD
4) Created a track at my new server and added imported SC
Then I have to import my SC from old server with sources and there is some errors happens for me.
First option: I have exported my SC from CMS, but the SCA file is about 5kB. I unzipped it and there was ARCHIVESOURCE folder but it hasn't anything seems to be my sources. That file is checked-in successfully through the transport studio, but no sources imported into DTR.
Second option: I have exported the SCA file by using NWDS. It's exported OK, size ~1.3MB, ARCHIVESOURCE folder with mine sources. But when I try to check-in it, it fails with an error "import failed, because the sources are not contained in the archive
Could anybody helps me to achieve my task? I stuck with source import.

Hi Kirill,
important to know that assembly ALWAYS uses the CONS/ACTIVE workspace for SCA generation.
If you for instance create a change (an activity), and you activate and release it but you don't import this activity into CONS, then it won't be part of the CONS/active and then due to obvious reasons assembly won't produce the sources either (no possibility to do an explicit activation on cons level as here a force activation takes place at import, but of course the import into cons is a necessary step, because as mentioned assembly uses the cons/active).
Can you please confirm/deny how this scenario looks like on your end?
Thank you!
Best Regards,
Ervin

Upgrade from Leopard Server

Hi
I have recently bought a different server and now have a redundant Mac Mini that I want to run as a desktop once again. I wanted to upgrade to Snow Leopard but can't from Leopard Server. Do I have to format the disk and start again or is there a better way of doing this please?
Thanks
Rich

CregyAbi wrote:
Hi
I have recently bought a different server and now have a redundant Mac Mini that I want to run as a desktop once again. I wanted to upgrade to Snow Leopard but can't from Leopard Server. Do I have to format the disk and start again or is there a better way of doing this please?
no better way. just boot from the SL install disk. reformat the drive with disk utility there and install. if you need the data on the drive clone the drive to a different one first.
Thanks
Rich

Migrate Notes from Exchange server 2007 to office 365

Hi,
Anyone help me to how to migrate notes from exchange server 2007 to office 365 . My customer having notes on his existing exchange account . We would like to move notes to office 365 .
Please help me or guide me .
Thanks & Regards,
Vinoth

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Please help, After mac 10.5.8 mail server migrated to snow leopard server?

Hi,
All my old emails date has changed to the date on which i migrated to snow leopard server, all the old emails show as they arrived on 31st of Dec 2009.
How do I fix it. Very Very important to me to have the arrived date.
Please help
Thanks,
Gulab Pasha

here is a link of other users having wrong date problems after upgrading to 10.6
http://discussions.apple.com/thread.jspa?threadID=2134525
Some people have managed to fix their date problems. The easiest workaround is to add the column "Date Sent" under (View->Columns->Date Sent) in mail.app and to sort by the send date not the received date.
Hope this helps

Problem connecting with VPN after migrated to SNOW LEOPARD SERVER,

Hi,
I recently migrated to Snow Leopard server, I have a strange issue when connecting to the VPN Server.
Please find the below error.
Fri Jan 1 14:38:22 2010 : CHAP peer authentication succeeded for jasmine
Fri Jan 1 14:38:22 2010 : DSAccessControl plugin: User 'jasmine' authorized for access
Fri Jan 1 14:38:22 2010 : MPPE required, but keys are not available. Possible plugin problem?
Fri Jan 1 14:38:22 2010 : sent LCP TermReq id=0x2 \"MPPE required but not available\"
Fri Jan 1 14:38:22 2010 : Connection terminated.
Fri Jan 1 14:38:22 2010 : Connect time 0.0 minutes.
Fri Jan 1 14:38:22 2010 : Sent 0 bytes, received 0 bytes.
Fri Jan 1 14:38:22 2010 : PPTP disconnecting...
Fri Jan 1 14:38:22 2010 : PPTP disconnected
2010-01-01 14:38:22 IST --> Client with address = 192.168.1.76 has hungup
Please let me know what is the cause and how can i fix it.
Thanks,
Gulab Pasha

Did you turn on the Printer Sharing in the "Share" preferences panel?
And, for Windows computers to access your printer, they need to install "Bonjour for Windows", which is a part of the iTunes+Quicktime install package, I believe.
Alternatively, you can turn on SMB sharing on your Mac, which is also in the "Share" preferences panel. You first highlight and turn on "File Sharing", then there is an "Options..." button to the right, clicke it and check the checkbox of "Share files and folder via SMB (Windows)".

Migrating wiki from 10.5 to 10.6 server

I am having trouble migrating my wiki from my leopard server to snow leopard server. This is the process I am doing.
1. create wiki group on snow leopard server with the same name as group on leopard server and turn off web service.
2. copied folder from /Library/Collaboration/group_name from 10.5 server to same location on 10.6 server.
3. edited ownership permissions to teamsserver:teamsserver on copied folder and sub-folders
4. rm index.db
5. edited GenereatedUID in the metadata.plist to match the GenereatedUID in Workgroup Manager for the group I created.
I am able to log in to the wiki and it takes me to the welcome that we have from the 10.5 server. The sidebar headings are the same. The problem is that I cannot see any of the entries or wiki pages that were created before. Is there something that I'm missing?

Here are the steps to manually migrate a wiki from 10.5 to 10.6:
sudo serveradmin stop teams
sudo mv $GROUP_DIRECTORY /Library/Collaboration/Groups/
sudo chown -R 94:94 /Library/Collaboration/Groups/$GROUP_DIRECTORY
sudo rm /Library/Collaboration/dataVersion.plist
sudo rm /Library/Collaboration/globalIndex.db
sudo rm /Library/Application Support/Apple/WikiServer/directoryIndex.db
sudo serveradmin start teams
You will then need to navigate to the wiki as an administrator and set the access permissions in the wiki's settings screen. There you can restrict access by directory users and/or groups (if you need that level of granularity).

HT5139 OSX server failed, need to migrate wiki from TM backup to a different existing (configured) server

I've looked and found many responses involving restoring from time machine to restore the complete server. In this case, I have a TM backup of the failed wiki machine and a second running (and configured) server. What I need to do is restore the wiki from this first TM backup to the "new" server.... but only the wiki data.
Currently, the "new" machine is NOT running wiki services at all.
Both machines were / are running Mountain Lion, so there should be no issues there.
I'm having some trouble locating a procedure for this. Any help is appreciated, and apologies in advance if I missed these instructions on some other post!
Thanks in advance for all the help!

Does http://support.apple.com/kb/HT5082 help at all? You would have to restore your TM backup to a separate disk, use that to startup, dump the wiki and postgres data to disk, reboot using your new server disk and follow the instructions to copy all wiki data to the new server.
Cheers
Gerry

How to upgrade from Leopard Server 10.5.8 to Lion Server?

In anticipation of Lion, I finally retired my G5 2.7GHZ Mac Desktop running Mac OS X Server 10.5.8 and moved the start up drive to an 2 GHZ Intel Core 2 Duo MacMini.
It is running fine.
I would like to now upgrade to Lion Server, but without spending $499 for Snow Leopard Server. I do have a Evaluation Copy of Snow Lleopard Server 10.6. Can I use this as an intermediary transition to Lion?
Any other suggestions short of spending the $499?

There is no way at this time to go from 10.5 to 10.7 with out extra steps.
If this is a Mac Mini and Not a Mac Mini Server you can get the 29.99 Snow Lep client disk and install client on the mac mini then install lion and server on it making it a server and then bring your data back
If this is a Mac Mini Server you can install it from a Snow Lepored Client Via target disk mode. then you can erase the drive and install fallowing this apple support document.
http://support.apple.com/kb/HT4766
Now Migration will only mode your data and not update the OS, so migrating is not the solution for you. if you where to buy a new machine with Lion installed then migrating your data would he a help, but to update the OS you need to have 10.6.7 or higher
or a secound machine and be able to do the install over Target Disk mode.

Migrating Wiki from MoinMoin

Our current wiki runs with MoinMoin and I want to migrate the information to the Mac OS X 10.5 Server wiki service. Does anyone know of a convenient way to import the MoinMoin files into Mac OS X (or export them from MoinMoin to Mac OS X 10.5 friendly format)? I don't need a full blown automagic solution, but a command line script or something to facilitate this job would be very helpful. Thank you.

Here are the steps to manually migrate a wiki from 10.5 to 10.6:
sudo serveradmin stop teams
sudo mv $GROUP_DIRECTORY /Library/Collaboration/Groups/
sudo chown -R 94:94 /Library/Collaboration/Groups/$GROUP_DIRECTORY
sudo rm /Library/Collaboration/dataVersion.plist
sudo rm /Library/Collaboration/globalIndex.db
sudo rm /Library/Application Support/Apple/WikiServer/directoryIndex.db
sudo serveradmin start teams
You will then need to navigate to the wiki as an administrator and set the access permissions in the wiki's settings screen. There you can restrict access by directory users and/or groups (if you need that level of granularity).

Migrating wiki from Leopard Server (10.5) to Lion Server

Similar Messages

Maybe you are looking for