i’m sorry – i don’t know about in-memory dbs and can’t seem to find anything. please check this doc :https://docs.oracle.com/cd/e59283_01/eppm/17/eppm_17_12_tested_config.xls

our company has migrated from 8.4 to 17.* version but we have encounter some problems in exporting files. some or most of the cost and resource values that we encoded have turn-out missing after exporting the file and our client receives an incomplete file. is there a work around on the matter or is there a new feature that is doing this and how can we correct it?

ruel

hi saboor,
it sounds like you are working on a copy of primavera p6 professional that is part of an enterprise install of primavera p6 eppm. in that case, you have to login to primavera p6 eppm to do any administration.
michael

in primavera p6 17.7 i don’t see the add user option in admin menu. i am no longer able to add new user or how? can any one help me?

thank you very much.

not at all. ms sql will always work and does work with p6 v17.x

i wish we did, but we don’t. that is why i wrote this long-winded explanation how to find lag.

that is not a new feature. you should be able to update the actuals against resource assignments in all versions of p6.

neeraj, thanks for sharing your experiences here. i’m sure 17.3 looks very different from 8.1.
the problem with the notebook character set – does it cause error or do you simply loose your old notebook entries?
m

hi,
we’ve just upgraded from 8.1 to 17.3 and everything went fine, except two things mentioned below;

notebook character set : due to database upgrade, there’s high chances that new database won’t support your old notebook character set. we resolved it in our env with bit of one time customized code

secure code : we were using secure code pretty much in our old env., in the new version secure codes are getting copied while copying the project and messing up the data. as we use secure code for filtering and layout.

the second one is still pending with oracle as an enhancement. other than that system is working perfectly fine and much better than old version

hi grinnell,
well upgrades don’t always go smoothly, but i’m sure project partners has you in good hands.the major risk is always loss of data. but it’s easily avoided with a backup prior to starting. typically, if the upgrade isn’t successful, there’s a strategy to ensure you can revert back to the previous version.
p6 upgrades are becoming more complicated as the software is evolving. i expect you may have to move from 8.3 to 16.1, and then to 17.3, but i’m sure your consultants have researched the proper steps. from that perspective, having mid-point backups is a good idea as well.
there’s no documentation on the upgrade risks. upgrading can be bumpy, but it usually gets figured out in the end, ideally with minimal downtime for your users.
the upgrade should be tested and proved in a test environment to ensure all of the steps are known and documented for when you perform the upgrade in production.
much of what i’ve said is it knowledge and not specific to primavera p6. hopefully that shed some light on potential risks.

i have a question. i am about to go through a p6 8.3 conversion to p6.17.3 (with project partners). can you tell me some of the major risks that i may encounter? is there a document in oracle knowledge base that discuss these risks.