Moving Universe from Development to Production

Hello Gurus,
I am working in XI R3.1.
I have modified an existing universe in designer. what are the things that I have to take care of before i export it to Production. In our company not using Import Wizard to move the universe from dev to production. we are moving the .unv files and reports to production using the manual method. i.e save the .unv file in a shared network and open it in production and save the universe.
Below are the steps that I am following. Please let me know If I am wrong.
1. Imported and modified the universe according to the requirements.
2. checked the integrity check and cardinality. there were no errors.
3. saved the universe and checked the radio button "Save for all users"
4. changed the connection to SHARED connection.
5. exported the universe to repository.
copied the .unv file from the USERDOCS where all the .unv files are stored to a shared network
6. opened the .unv file in production environment. changed the connection to secured and saved the universe and checked the radio button "Save for all users."
7. Imported the universe to production repository.
Am I following the correct steps. Please shed some light.
Thanks,
Naveen

Hello Naveen,
did you also look at the LifeCycle Manager tool that is available for download to help you to move objects from Dev to QA to PROD ?
thanks
Ingo

Similar Messages

Ora -20001 When moving application from development to production

Hi,
I am currently trying to get this application to successfully to update but i am receiving the below error message.
The action I am performing is trying to update a record via a save button.
This issues an SQL_UPDATE to Automatic row processing.
ORA-20001: Error in DML: p_rowid=5718074, p_alt_rowid=PERSONAL_ID, p_rowid2=, p_alt_rowid2=. ORA-20001: Current version of data in database has changed since user initiated update process. current checksum = "F6632C5E819349C1307E25A54BBD2F93" application checksum = "0"
This is not happening on the development application or when I access the application via the admin login. It is only when I use the following url:
http://<server>:<port>/pls/htlmdb/f?p=101 I get the error.
Both versions of APEX are 2.2.1.00.04 and using IE 6.0
I have checked various entries in the forum but they do not fully meet the scenario I am getting,
Any help will be greatly appreciated.
Many thanks
Ty

oops wrong forum
Message was edited by:
user522107

Questions on Analyzer Upgrade and Moving Analyzer Reports from Development to Production

Hi,We run Analyzer 5.0.3. We are planning to go to Analyzer 7.2. Did any body go thru this upgrade? If so, what is your opinion and tips that may help. Also, we never had Analyzer development environment. We are planning on having Analyzer development environment. In our installation, all of the Analyzer reports are centrally developed based on user requests. Once we have development and production at the same Analyzer version, if a report is developed in the development system, how can the report be mirateed/moved from development to production system?Thank you for your help,Prasant

Balaji,
Has this been done yet?
Gary
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by [email protected]:
We are working on a document using which one should be able to move a portal instance from one database to another. It is still in draft version, once it is finalized we will be putting it on otn.
Thanks and Regards
Balaji<HR></BLOCKQUOTE>
null

Process of moving TR from Quality to Production

Dear Experts,
we are in a process of moving TR from Quality to Production. While moving we faced transport incositencies like some old requests have been overwritten into the new one and dependant objects were failed during import in PRD. Now production rehearsal client is kind of messed up. what is the right procedure to transport the requests from Quality to Production. (actually we transferred the TR individually based on the list send by the respectivr module owners). Please help me to findout the solution for this issue.
regards,
Yasin.

Hi,
This situation comes every now & then when you don't have any client strategy define in your landscape I'm not blaming you but for your Project Manager and then rest of the team adopt SAP standard practice if you really want things to go well act NOW..!! here is the basic to start:
Ex,
DEV ::
100 => Golden Client
200 => Customizing Client
300 => Test Client
Things to check before importing request in QAS :
1) Always get the request in sequence format ask the owner of the request for the sequence to avoid dependency issues
2) Technical Specification doc - this doc will be prepare by Functional / Developer on what changes are included in TR
QAS::
400 => Quality Client
Things to check before importing request in PRD :
1) User acceptance doc i.e UAT - client / customer will check the functionality if it's on then move this to PRD
2) Get the request in sequence format
3) Approval for production transport
PRD::
500 => Production Client
Thanks,
Saleem

Migrate Webi Report / Universe from Dev to production

Hello,
there are lot of possibilities to migrate a Webi report or a universe from Development server to Production server. my question for the experts is what is best practice scenario to do that. What should i take in consideration.
if i rename my Production universe, place it in an other Path and base my migration on the option "compare name and Path" of the universes. would it migrate ? What about the Connection ?
My Target when migrating Universes. Is only to migrate the universe without connections
But when migrating Webi Reports is to migrate only the reports without universes or connections. But at the same time be sure that the Report is adressed to the right universe in the Destination System.
Is that realistic .. Thanx ..

Prerequest:
You should have Remote access to both the server the BO is installed
Approach1:
Login to source server
create a folder with the name temp.biar in the desktop of server 1
Go to import wizard of server 1
select server 1 as source and temp.biar file as a destination and import all that required to biar file
from server 1 connect to server 2 and place this biar file in some shared folder
connect to server2
open the shared folder and copy that biar file and place it in the desktop of server2
Go to import wizard of server 2
select the temp.biar file from desktop of server 2 and destination as server 2
and complete the process
Note: as we are doing this in remote, there will be lot of issues while connection to path which sometimes even the erro r message will mislead us....
Approach2:
dont create any biar file
Login to server 2
Go to import wizard
select server 1 as source and server 2 as destination and move directly from server to server
Approach2 is not preffered if server 2 is production serve....
this may help
Thanks,
-Ganesh

ERROR WHILE MIGRATING SSIS PACKAGE FROM DEVELOPMENT TO PRODUCTION IN EXECUTION

HI,
I have a problem while executing the package after migrating from DEVELOPMENT to PRODUCTION.
We have two SQL database connections DEVMIDDLEWARE and PRODMIDDLEWARE for dev and prod respectively. When we have created package in development we have used DEVMIDDLEWARE and we have credentials in CONFIG file of that package and executed sucessfully. When
we migrated this same package to PRODUCTION when have given credentials of PRODMIDDLEWARE in CONFIG FILE of this package we are getting error as below
"Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic
error. Verify that the correct key is available. End Error Error: 2014-10-28 07:41:44.24     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC0202009     Source: Package Connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware"     Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.".
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC020801C     Source: Package Log provider "SSIS log provider for SQL Server"     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method
call failed. COM error object information is available. Source: "Package" error code: 0xC0202009 Description: "SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE
DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.". ". End Error Error: 2014-10-28 07:41:44.98
Code: 0xC0202009     Source: Package Connection manager "AGRDB01.abwr66"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record
is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'CC\epsdbuser'.". End Error Error: 2014-10-28 07:41:44.98     Code:
0xC020801C     Source: Data Flow Task OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "AGRDB01.abwr66"
failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC0047017
Source: Data Flow Task SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC004700C
Source: Data Flow Task SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-10-28 07:41:45.00     Code: 0xC0024107     Source: Data Flow Task
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 07:41:44 Finished: 07:41:45 Elapsed: 0.859 seconds. The package execution failed.
The step failed."
Can anyone help for this error.
Many thanx in Advance

Hi Babloo,
According to the error message, the package may have failed are as follows:
The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
The package may not run in the following scenarios:
The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Run an SSIS Package Under a Different Account
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS package fails because of excel connection manager when deploying package from development to production

Hello,
When I move the package from development to production package fails due to excel connection manager.
Error message---
Message
Executed as user: Answers\Administrator. ...lt: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source... The package execution
fa... The step failed.
Any help would be appreciated.

Hi Vinay,
As Visakh mentioned, the issue usually occurs because the package runs in 64-bit runtime, however, the Excel driver is 32-bit. According to your another thread, it seems that you use SSIS 2005, right? In SSIS 2005, there is no “use 32 bit runtime” option
for the package executions of a SSIS package job step. In this condition, you have two choices:
Install the 64-bit Microsoft ACE OLE DB 12.0 Provider on the production server. Here is the download link (AccessDatabaseEngine_x64.exe):
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Create a CmdExec type job step instead of SSIS Package job step, so that we can call 32-bit DTExec.exe to execute the package within command line. For more information, please see:
http://support.microsoft.com/kb/934653/en-us
Regards,
Mike Yin
TechNet Community Support

How to transport the data contains in the table from development to product

How to transport the data contains in the table from development to production.
Please let me know ASAP.

Hello Dilip
Create a workbench request and add the following entries to the request:
Object key: R3TR TABU <name of z-table>
For this object add the following value key:
- client-independent table: '*'
- client-dependent table (e.g. client 100): '100*'
See also: [SAP Network Blog: Transport Table Entries|/people/community.user/blog/2007/01/07/transport-table-entries]
Regards
Uwe

Query related to request transfer from development to production server.

Hello,
I am transfering request from development to production server , the error occured is object REPT of particular program is inactive.
What is this error ?
Plz give answer as early as possible .
Thanks in advance.
Vikram.

Did You try my solution'
Hi..,
go to the request in SE09...
in the menu
Request/Task->Complete Check-> Display Inactive objects..
you will get the objects which are inactive and u can active them there itself.
santhosh

Transport Web Template, Query from development to productive system

Hi!
How can I transport Web Template, Query, workbooks from development to productive system?

RSA1 ---> Transport Coonection ---> Object Types -
> Select Web Tempelate ---> Drag to right and group under transport
Similary do for other objects
Thanks
Amit

OWB propagation from development to production environment

Our department is in need to implement overall security around our production data warehouse.
One issue that seems to bother our management is having only one OWB Designer where developers would have to be responsible enough to use snapshots and export mappings to mdl files. Management would like to have development and production OWB Designer Repository where production designer would always be in sync with what is deployed in prd database. Also prd OWB Designer Repository would be like a source safe so we have to always get a mapping from prd designer move it dev designer and when done propagate changes back to prd designer and then deploy to prd database.
Would this be a good approach?
Any input on how to handle propagation from development to production environment, and if you are aware of "best practices" when it comes to OWB environment is appreciated.
Best Regards,
Vlasta

Hi,
Copy whole catalog and rpd from dev to prob.
If you want to copy specific report go to OracleBIData\web\catalog\samplesales\root\shared\sample+sales(group folder name)
You can copy reports under folders and dashboards in _portal in Sample sales group folder...both file and .atr file.But you may miss security applied on those dashboards.
http://www.rittmanmead.com/2008/04/28/migration-obiee-projects-between-dev-and-prod-environments/
Best practice is to copy whole catalog and rpd (or) Copy shared and system folders and their .atr files from OracleBIData\web\catalog\samplesales\root so that you will not miss security and you will not over ride users folders which may contain some data created by them.
Thanks,
Srikanth

Error while importing the ODI Package from Development to Production Enviroment

Hello Everybody,
Currently I'm face the problem when import ODI models (from Development) to Production environment
And the error show follwing error:
ODI - 23040 Import file "C:/BIAPPS_Package/Models/XyZ.xml" error
please help.

Do the user performing the import have permissions to import models to the production environment? I'd also mention that you would have a better setup if your production environment only held executables such as scenarios, load plans etc. and not development objects. It leads to better change control management and simplifies the migration process from DEV --> PROD

VC Reports transport from Development to Production

Hi all,
     How do we transport the VC Reports from Development to Production.
     How to transport the model.
     Do we need to create new System Object.
     please help me. Are there any standard document available.
Thanks & Regards,
kishore.

Hi
After importing the model as Dharmi explained, you might need to change the systems' names in the model to fit the production landscape. For example, if a backend system has an alias AAA in Dev and same system has alias BBB in prod. To do this, simply choose Tools > Manage services...
If the landscapes are compatible, you can transport only the working iView using the portal transport capabilities. Navigate to System Configuration > Transport in the Dev portal, find your iView and add it to a transport package.
Hope this helps,
Shay

Problem in moving Set_pf_status from pquality to production syatem

Hi,
I came across one strange incident while transporting code from Quality to Production. I could see the module set_pf_status in tcode se51 in the quality system. When I transported the code, I could see only module %_pf_status in the tcode se51 in the production system. The transport requests are successfully moved to production. But why all the code is not in the production. Could anyone please help me.
Regards,
Satish Kanteti

check the transport sequence for this object?

In Oracle How to migrate .Rdf file from Development to Production Environ..

Hi,
Please explain me step by step how to migrate report(.Rdf) file from development instance to production instance ASAP.
Thanks & Regards,
Raj

Rai,
Please ask your questions in the EBS section, since they are not PeopleSoft related.
Regards,
Hakan

Moving Universe from Development to Production

Similar Messages

Maybe you are looking for