Application content migration manually from EP 6.0 to EP 7.0 EHP1

Hi All,
We have EP 6.0 portal system running on windows 2003 server and oracle .We have another EP7.0 EHP1 portal system installed on AIX 6.1 and oracle. The present portal is connected to BW, CRM and ECC systems and
also lot of customization is done in NWDI. The customer is requesting for manual migration of Iviews, user, roles, customized applications etc. from EP6.0 to EP7.0 EHP1.
Is it possible to go ahead and do?
Any implication are there?
Please provide your valuable suggestions and feedback in this regards.
Thanks & regards,
Vidyadhar K

Hi,
I don't think so it is possible because version of both the portals are different. So, might be you can face some issue.
Thanks
Sunny

Similar Messages

Reasons Adobe should write a migration manual from FH to AI

what my friend wrote me...
About FHMX, how about educating people why Freehand is so
much better than
ill, and publishing a migration guide from ill to Freehand.
Maybe you and I
can join Adobe and implement this program! As a matter of
fact I've already
written the introduction to the guide.
Top reasons why I love using Freehand MX over Illustrator for
the work we
do. Try it, and you'll like it too.
•Gouping and ungrouping is time consuming in ill. If an
object on the bottom
is grouped, the whole group is selected. Selecting the bottom
object is
useless unless you ungroup all. Very time consuming.
Freehand can select one element even if it's part of a group.
• It is common in ill & FHMX to hold down shift
while clicking on objects to
select several at a time. ill has a tendency to 'pick up'
& move those
objects as your moving from one to the other. Which means
having to back up
your last step and then continue.
•• ill select/same/stroke colour, fill colour
etc. VS FHMX 'find & replace'
In ill available only 'document wide' which forces you to
take the selection
and place it in a new document (usually a temporary measure
ill forces upon
you).
All this copying takes extra time when the art is complex.
Since changing colours is often the goal, opening a new
document means
having to drag into the new doc, all the colours you'll be
needing to
change.
Also when choosing same fill & stroke colour, ill doesn't
catch everything,
so you have to try several times to get everything.
FHMXs 'find & replace' runs on whatever you select,
without requiring
copying
the info to a new document, so there is no waiting like in
ill. And it
catches everything all in one shot. Wham, bam thank you maam.
FHMXs 'find &
replace' light years ahead of ill.
• Multiple page documents
FHMX multi page documents can be of different sizes and
orientation within a
single document. Ill must have the same size and orientation.
Ill allows only one page size & page format while FHMX
permits you to use
any combo within the same document, all with the click of a
button. Job's
done.
ill: go into doc setup and calculate new overall width.
"let's see I need 5 pages of 8.5x11 so that's 8.5" x 5 pages
=42.5" width.
If you add a page, all the doc info gets shifted off center.
Ill requires
you to select all, (make sure nothing is locked!) and
recenter all the
pages. All time consuming and unnecessary in FHMX.
Ill can't handle multiple pages when it come time to print
them all. In
order to be able to print an 8 page document with simple
vector art (without
any linked files) in illustrator, it was necessary to convert
the document
to 8 single page documents. Each page took 5 minutes , 40 min
total.
FHMX prints multiple page documents with no hesitation.
••ill has no collect for output. This is
ridiculous. FHMX enables you to
enjoy creating freely without having to think of where that
tiff you just
imported came from. When the art is finished in FH, click
'collect for
output' and in under 5 seconds a complete folder is created
of everything
you need to backup that artwork.
Never spend one second looking for anything again when
opening a freehand
document. Not today, not tomorrow, or in three months.
In ill, after the art is done, you need to spend the time
looking for those
linked files, to gather them into a folder. And when a
deadline is so
important, will you actually take the time? NO! So days,
weeks, or months
later, when you need to open the file and the tiff is
missing, well, I hope
you like treasure hunts, because with time tiffs can be moved
or go missing.
With this one feature, FH saves hours of time per year over
ill.
•Pathfinder/combine in ill is slow ad often crashes the
program. (See next
point) Freehand unite is Fast!. ill requires you to ungroup
all elements
before using the filter. FHMX doesn't.
••Paste inside.
FHMX enables you to use garment sketches without modifying
shapes to
accommodate a tiff pasted inside. Tons less work over ill.
'Paste inside' in
FHMX is fast & effortless, encouraging you to paste
inside each individual
shape of the garment. (Ex. Belt loops, waistband, pockets,
body. All get
their own tiff pasted inside.) This gives the artist freedom
over each
individual tiff. Changes can be applied in light/dark or
angle to each tiff
seperatly from one another.
Ill cannot do this without a massive investment in time, it
doesn't even
compare with the ease of FHMX. ill method is also a pain to
work with ,
requiring you to lock/unlock items as the masks bounding box
is often in the
way. This requires you to lock nearby elements in order
select. Very
annoying. This work around is so time consuming it
discourages you to paste
inside individual shapes. In fact it's impractical to do so.
You're forced
to combine all shapes and paste one tiff into this one
overall shape, which
is time consuming because it increase your workload to
achieve a lesser
result.
Ill requires you to draw a duplicate shape which must lie in
perfect
register with the shape underneath it. Shapes are often
composed of highly
complex components (ex:text) that need to be united into one
overall shape,
to paste into. Often these complex shapes crash illustrators
unite filter,
making the job time consuming or impossible. FHMX requires
none of this
workaround, because FHMX enables you to past into individual
shapes.
FHMX can even paste inside a paste inside, and in easily
accesible layers,
creating realistic effects. Don't even dream of doing this in
ill.
•ill toolbox. The 'Venus' girl at the top of the box is
often clicked in
error resulting in an annoying 'Adobe online' dialogue box
appearing. So
annoying! Bury this feature elsewhere, or at least move it
away from the two
arrow tools, the two most used tools of the whole program!
Stop interrupting
workflow!
•Ill locking unlocking frenzy
You'd like to add a point to a path. In FHMX, select the path
and click on
it
with the pen tool. You're done.
In ill, select the path and click on it with the pen tool +.
But ill adds
the point to the path in front, even though you selected the
one in back!
Ill forces you to lock the front path to get to the rear
path. If your
artwork has many layered paths, get ready to go on the usual
locking frenzy
until you get to the path you need. All this just to add a
point.
As an added bonus, ill often throws the "Can't add an anchor
point. Please
use the add anchor point tool on a segment of a path"
dialogue box in your
face, as if you can't aim a point on a path.
Paste inside
• Because paste inside in ill is so complicated, a
common workaround is to
create a pattern swatch to achieve the same ease as in FHMX.
However pattern
swatches are simple vector paths that can't match the
subtlety of a tiff.
When opening a new document, swatches have to be brought in
to the new
document to be used.. When changing a pattern colour, a new
swatch has to be
created, which is more time consuming than changing the tiff
colour in FHMX.
5 seconds vs. 5 minutes
• The arrow+ tool in Ill selects in increments of one
group at a time. FHMX
selects in increments of one element at a time, giving the
user greater
control over elements within groups.
• In Ill before using Pathfinder/Unite, you should
save, because pathfinder
tool often crashes the program. Since large documents take
time to save,
waiting time in Ill multiplies. FHMX doesn't crash when using
the pathfinder
tool so much time and frustration is saved.
Sometimes Pathfinder in Ill just won't work the way it's
expected to. I wind
up importing the art into FHMX where it works fine and
instantly.

I think what Morty said needs to be reminded here:
quote:
quote:
Should we read anything into Adobe putting out the Freehand
to
Illustrator migration guide you posted about?
No, that's something that Adobe has planned for quite some
time. I hinted to its release several months back when we were all
discussing how Adobe should produce such a document. This "rumor"
that I refer to is something that surprised me as well. I have yet
to confirm it though...
Mordy
Since Adobe was planning this for some time, let's not jump
to conclusions. Mordy did confirm to us that there is indeed a
Product Manager for FreeHand. Also, it's interesting to note that
Adobe has a different situation on their hands than they did with
Pagemaker. What we have is two competing (?) programs, FH and Illy,
they are both truly loved by their devoted users. Adobe probably
realizes that they gave to keep both because the users of either
program have been devoted for years. Neither Illy or FH users would
be happy about migrating. Adobe I'm sure will keep both programs
(at least I'm hoping they are smart enough to). When Adobe migrated
Pagemaker users to InDesign, InDesign was a new tool. Illy is old
like FH...you ca't force a migration to a tool that is just as old
as the one your migrating from.

OBIEE 11g - Application role migration from DEV to UAT or to PROD

Hello All,
there are blogs which mentioned about application role migration from dev to UAT or Prod..
Kindly provide the correct path of below two files which we use for application Role migration
1. system-jazn-data.xml
2. jps-config.xml
I have searched these files but noticed there are 3 or 4 files with same name under different paths.
Kindly help. TIA
Regards

if you mess up these files, your system will get corrupted.
You need to take proper back up and then get it done.
another way where you can avoid this risk is to manually enter the roles. Creating roles is one time effort unless you keep deleting and creating new roles. If you manually do it you will have more control on migration and you can fix if there an issue easily. Note, the migration of roles does not map the groups to roles . You still have to manually map them.
OBIEEHOME\user_projects\domains\bifoundation_domain\config\fmwconfig
1. system-jazn-data.xml
2. jps-config.xml

KM content migration from EP5. to NW2004s

Hi all,
Can you tell me if its possible to migrate KM content from EP5.0 to NW2004s?
I know that the only scenario supported by SAP is the migration from 5.0 to 6.0 and then upgrade to NW2004s.
But are there any tools that could be use to perform this migration directly from EP5.0 to NW2004s?
Thanks and Best Regards,
Paulo Ruivo

Hi Paulo,
As suggested by SAP recommended way is to migrate from EP5.0 to EP6.0 then upgrade to EP7.0.
No ,there are no standard migrating tool for migrating content as the way u want.I am afraid you may have to do it manually.
Regards
Rani A

How to delete file manually from application data base

Hi All,
Could anyone tell me how to delete file manually from application database.
Thanks In advance
Regards
SAN
Edited by: Sanjay Nair on Sep 2, 2008 10:51 AM

Closed

KM content Migration from EP 5 to Ep7

Hi There.
We are trying to migrate Km content from EP5 to EP.. i know that this can be achieved through ICE. and i have seen couple of blogs also but i am still not able to get any step by step info.. along with all pre-requisite..
Can you please share your experience and methods in KM content migration using ICE.
Thanks for your help.
Rgds

Sudhir,
this <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/38effdbf-0d01-0010-c3ad-9d9547a492af">How To ... Distribute KM content using the ICE protocol</a> should still make it..
rgds

How to content migrate from e-room to sharepoint using powershell

Hi,
How to do content migration from e-room to share-point using powershell.
Please give step by step process and give some idea about migration using powershell and other tools.
Thanks,
inguru

Hi,
There is no direct content database migration approach from eRoom to SharePoint.
However many third party tools such as Metalogix, Tzunami, and AvePoint are available to migrate eRoom content to SharePoint as well as you can write your own utility
to migrate content since there are various eRoom API available for the same.
Thank You, Somnath Matere

Migration guide from Iplanet application server

Hi ,
i would like to migrate application to oracle 9ias application server.Curently we are using iplanet application server6.5.
From where do i get some useful documents.
In oracle 9ias faqs , its written that its available on http://ias.us.oracle.com.But the site is not opening up.
If some one has already tried migration please suggest to us as how to do.
Thanks in advance
smita

Please refer to the following url:
http://www.sun.com/migration/sunonetools.html
This should give u a head start on what needs to be done and how,. WIth respect to webserver , i guess you can use it or leave it depending on the architecture you require to deploy your solution.
Hope this helps !

How to change the name of HFM EPMA Application while migrating from dev to

We have HFM EPMA application in Dev env on 11.1.2.2. We want to migrate aplication to production environment with different name. We are using Life cycle management to migrate the application. I know life cycle management but do not know how to change the application name during migration.
As we have EPMA application so copy utility will not work. Please helop.

Hi ,
You could use the Copy app utility to migrate the application from Dev to Prod.You could have your desired app name while setting up the copy process.
The EPMA application from Dev will be converted to an Classic application in Prod after the copy.
Then you might need to use the "Transform Classic to EPM Architect" and convert it to an EPMA application.
So your Application with the data from Dev will be moved to Prod.
To Navigate ,
Launch Workspace
Navigate ->Administer->Transform Classic to EPM Architect
Thanks and regards,
Gunasekaran rayar
Edited by: Gunasekaran Rayar on Nov 28, 2012 5:04 AM

Content migration from old to new database server

There is thread upon thread upon question (as well as answer upon answer) of this already. I have 3 farms running concurrently. 1 production, 1 development and a new production (farm A, B and C respectively). Farm A's databases are on SQLa\SP while Farm
B is on SQLb\Beta and Farm C on SQLb\SP. I've successfully copied the content database over from Farm A to Farm B & C without an issue. Farm A and C are identical except for server names (service accounts etc).
What I'm trying to do now though is just a simple content refresh from FarmA to FarmC. Aside from shutting down FarmA and C, backing up & restoring the database again, is there another way to do this?

Hi,
According to your description, my understanding is you want to find another way to change farm A production environment to farm C production environment aside from shutting down FarmA and C, backing up & restoring the database .
It involves moving a farm.
Moving a farm typically involves the following steps:
Set up the new server farm
Move the databases to the new server farm
Shut down the old server farm
So how to move the databases to the new server farm is the point. For moving all the databases, you can backup and restore. Another way is detaching and attaching as the thread states:
http://sharepoint.stackexchange.com/questions/25215/the-best-practice-for-moving-content-database-between-two-farms
But copying the files is also a dangerous option due to file locks etc, and you don't want to take down the farm just to copy the data.
For more information, you can have a look at the blog:
http://www.codeproject.com/Articles/664029/Migrate-SharePoint-s-SQL-Server-to-another-SQL-Ser
Best Regards,
Eric
Eric Tao
TechNet Community Support

I'm wanting to migrate certain applications from my MacBook Pro over to my newer Mini, but Migration Assistant doesn't allow doing this by choosing which applications to migrate-how can I pick only certain ones?

I'm wanting to migrate certain applications from my MacBook Pro over to my newer Mini, but Migration Assistant doesn't allow doing this by choosing which applications to migrate-how can I pick only certain ones?

You only bought it four months ago, so it's still under warrantly.
Call Applecare or call your nearest Applestore to make an appointment. Tell them your mac has serious technical issues, describe them shortly.

HT1926 i have installed quick time ok but not itunes get an error code and tried downloading manually from tools but still no good. also get verify i have sufficient priviledges on apple mobile support and application ?????

Hi all. I have tried installing itunes and quick time many times and have finally got quicktime but no itunes . I have followed apple support and disabled anti virus and everything etc and also tried installing itunes manually from tools but still get error code. also when getting to apple mobile support and starter etc i get verify that i have sufficient priviledges ? Anyone know what the heck all this is about guys ?????

SadisticIron wrote:
i just baught my first iphone and it is a jalbroken
Buzz! Thank you for playing!
Discussing jailbroken devices is forbidden here by the Terms of Service.
You can not get help here.

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

Migration Assistant from PowerBook 10.3.9 to new MacBook Pro?

A friend has just bought a new MacBook Pro. His previous Mac is a PowerBook (G4 1.0 GHz 15" FW800 - Aluminium) still running Panther 10.3.9.
He's asked me to help him migrate his files, settings, apps etc. to the new Mac. I had thought to use Migration Assistant/Setup Assistant to do this, but the manual for the MacBook Pro says:
+"Before migrating, use Software Update on your other Mac. The other Mac should have one of these versions of Mac OS X software—either Mac OS X v10.4.11 or Mac OS X v10.5.6 (or later)."+
Does this mean you can't migrate from a Panther Mac to Snow Leopard using Migration Assistant?
TIA,
Chris Adams.

You use Migration Assistant from the new machine. The old machine needs to be started into Target Disk Mode. Both machines need to be first connected via Firewire cable. See the following:
A Basic Guide for Migrating to Intel-Macs
The Knowledgebase article Intel-based Mac: Some migrated applications may need to be updated refers to methods of dealing with migrating from PowerPC chips to Intel with the Migration Assistant safely. The authors of this tip have not had a chance to verify this works in all instances, or that it avoids the 10.6.1 and earlier Guest Account bug that caused account information to get deleted upon use of the Migration/Setup Assistant. However, a well backed up source that includes at least two backups of all the data that are not connected to your machine will help you avoid potential issues, should they arise. In event it does not work, follow the steps below.
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, copying the critical contents to CD and DVD, an external hard drive, or networking
will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.
If both computers support the use of Firewire then you can use the following instructions:
1. Repair the hard drive and permissions using Disk Utility.
2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.
3. Connect a Firewire cable between your old Mac and your new Intel Mac.
4. Startup your old Mac in Target Disk Mode.
5. 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.
If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)
1. Set up a local home network: Creating a small Ethernet Network.
2. If you have a MacBook Air or Late 2008 MacBook see the following:
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- Migration Tips and Tricks;
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
MacBook Air- Migration Tips and Tricks;
MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.
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 1/6/2009

Migrating data from a dead iMac

My 2006 iMac has died. The display does not work anymore. I have a new mini on order and I have a couple of questions about migrating the data from the HDD on my old iMac to my mini.
I do Have a time machine backup on a separate drive. I could not find anything that spoke about migrating to a new Mac from a time machine backup.
my questions are.
can I migrate from my old iMac to my new mini using a time machine backup?
can I select what data I wish to migrate?
how can I deauthorize the old iMa?
thanks

One of the first screens that will appear when you start up the new Mac will say "do you want to restore from another Mac or Time Machine backup?". Select that and follow the prompts. I could be mistaken, but I don't believe you can select what data is migrated (only what date you restore it from). Older system files will not be migrated (ie, your new Mac will have whatever OS it shipped with, not that of your old iMac).
if the old iMac powers up, you may still be able to migrate from it. Hold down T on its keyboard as you boot it up, and connect a FireWire cable (with Thunderbolt adaptor for the new iMac) across the two computers. You should be able to choose it as a migration source when you start up the new iMac; if you skip the migration at setup, you can try again using Migration ASsistant from the Utilities folder. Doing a migration instead of Time Machine recovery should give you a little more control over what gets migrated. Or you can skip automatic migration altogether if you want to select specific documents and files and do manual copying from one to the other (this won't work with applications).
Your last option would be to physically remove the Mac's hard drive and put it in an external enclosure (probably USB3 is cheapest) if you want to do a migration but can't power up the old iMac.
Unless you can connect an external monitor to the old imac to get it working, you might have to skip iTunes deauthorization until you have 5 computers authorized, at which time you can deauthorize them all from your iTunes account screen (and then re authorize the ones you're using).
Matt

Application content migration manually from EP 6.0 to EP 7.0 EHP1

Similar Messages

Maybe you are looking for