Migrating database views between instances

I've discoverer folders based out of database views?(around 30-40) and i'm planning to migrate all the VIEW's from one instance to another
I'm currently executing 1 by 1 and since, these views are growing in number with the requirements i was wondering if there a easy way/tool to achieve this.

Hi
In addition to the advice already given, are you also changing the owner for the views? If you are then you will need to update Discoverer to tell it who now owns them.
Should you move a view from one schema to another, use this workflow to update Discoverer.
1. Launch Discoverer Admin.
2. Open the business area containing a view that had its owner changed.
3. Right-click on the folder and from the pop-up select Properties.
4. Click on Owner and from the list of users, select the new owner
5. Click OK to return to the Folder Properties dialog box.
6. Click OK to close the Folder Properties dialog box.
7. Right-click on the folder again; and from the pop-up list select Refresh.
8. As you only have one option, click Finish.
9. Discoverer will now compare the data definitions for the object and hopefully you will have no differences.
If you do have differences this means there is something different in the new view and you will have to determine what that is and then fix it.
Does this help?
Regards
Michael

Similar Messages

Primavera P6 migrating Database to another instance with migrate.sh

I want to migrate an existing Primavera P6 Database to another instance.
What I have done so far.
I fully backed up the database with expdp and impdp, but I get an error while trying to connect with admuser (maybe because its not existing).
So I did not take more time in that.
Later I wanted to use the migrate.sh Tool which looked not that hard to do, because it only needs the credentials and Database connection Information.
The Database is large, that means over 14GB so I tried several times and the migrate.sh tool gives me after hours SQLExceptions.
So what should be the Problem?
Maybe the session time?
How to change?

Thank you for your quick reply.
Ok I will do the impdp import.
I found an db script: orpm_create_users.sql which will do the creation of all users.
But before I do that I got an error in the migrate.sh which says:
"Error in Run SQL Script orpm_ins_aux.sql : DatabaseToolException (ORA-02298: cannot validate (ADMUSER.FK_UPLIST_USESSION) - parent keys not found)
Do somebody has an idea for that?
I will post my impdp import after Ive done it...

Developing database views between Oracle and SQL Server tables

I am on Oracle 10.2, my organization has many SQL Server databases as well and has now made
SQL server as company standard so many new databases will be developed in SQL Server. It is of course
not possible to convert all Oracle databases to SQL Server, so a mix environment will exist. Two questions:
1. Is it possible to develop database views in Oracle (10g in my case) which join Oracle tables with tables in SQL Server 2008? If yes, how. I have seen some heterogeneous connectivity setup to connect SQL Server to Oracle, but not sure whether it is possible to develop a database view across two databases.
2. I know it is not a SQL Server forum, but many DBA’s know both Oracle and SQL Server. Is it possible to develop views in SQL Server (SQL Server 2008 R2 in my case) which join Oracle 10g and SQL Server 2008 tables? I know in SQL Server, there is way to set up linked servers, but do not know whether it is possible to develop views.
Thanks a lot for your insight.

You can create views that join local Oracle tables and remote SQL Server tables. I'm pretty sure you can do the reverse as well but I haven't personally done it.
However, I would be very concerned about the performance you'd get if you created that sort of view. You'd very frequently end up in a situation where Oracle has to pull all the data in the remote table across the database link in order to apply predicates and join the data locally. That could be disastrous from a performance standpoint.
Justin

FNDLOAD: Migrating Item Templates between instances

Hi All,
Can we migrate Item templates from one instance to another using FNDLOAD. If so can you please provide me an example or useful source.
Thanks a lot.

I do not believe you can use FNDLOAD. iSetup has the functionality to migrate item templates. See the iSetup User Guide at http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120azug.pdf
HTH
Srini

What are the differences between the following Oracle database views?

What are the differences between the following Oracle database views(or function)? Can they be instead of each other? Can all of them be used to pull out the execution plan from the library cache?
V$SQL_PLAN
DBA_HIST_SQL_PLAN
dbms_xplan.display_cursor function

junez wrote:
What are the differences between the following Oracle database views(or function)? Can they be instead of each other? Can all of them be used to pull out the execution plan from the library cache?
V$SQL_PLAN
DBA_HIST_SQL_PLAN
dbms_xplan.display_cursor functionV$SQL_PLAN-this is dynamic perfomance view which contain execution plan information for each child cursor loaded in the library cache.
DBA_HIST_SQL_PLAN- data dictionary view also contain execution plan information for each child cursor bun in workload repository.Actually this view captures information from V$SQL_PLAN and is used with the DBA_HIST_SQLSTAT .
dbms_xplan.display_cursor - function displays explain plan of any cursor loaded in the cursor cache. See more information below links:
http://youngcow.net/doc/oracle10g/server.102/b14237/dynviews_2120.htm
http://download.oracle.com/docs/cd/B14117_01/server.101/b10755/statviews_2154.htm
http://download.oracle.com/docs/cd/B12037_01/appdev.101/b10802/d_xplan.htm#998179

Column 'Blocked' of view v$instance in Oracle Database 10g

Hi All,
What is the description of column "blocked" of view "v$instance" in Oracle Database 10g?
I could not find the information in Oracle® Database Reference
10g Release 2 (10.2)
Thanks and Regards,
Vaibhav

SQL> describe v$instance
Name Null? Type
INSTANCE_NUMBER NUMBER
INSTANCE_NAME VARCHAR2(16)
HOST_NAME VARCHAR2(64)
VERSION VARCHAR2(17)
STARTUP_TIME DATE
STATUS VARCHAR2(12)
PARALLEL VARCHAR2(3)
THREAD# NUMBER
ARCHIVER VARCHAR2(7)
LOG_SWITCH_WAIT VARCHAR2(15)
LOGINS VARCHAR2(10)
SHUTDOWN_PENDING VARCHAR2(3)
DATABASE_STATUS VARCHAR2(17)
INSTANCE_ROLE VARCHAR2(18)
ACTIVE_STATE VARCHAR2(9)
BLOCKED VARCHAR2(3)
SQL> select version from v$instance;
VERSION
10.2.0.2.0

Migrate scheduler jobs between 2 databases

Hello,
I'm working on migrating a tablespace between 2 databases on different platforms.
I'm using DataPump for export/import, and I'm using the CONTENT=METADATA_ONLY parameter for the export/import of schema and tablespace.
The schema owner has some scheduler jobs on the source DB, and after the migration, the same jobs appear on the target machine, but the ones with arguments cannot be run - I saw a bug (#5239417) exists on MetaLink on this subject - cannot migrate scheduler jobs with arguments if the above export parameter is used.
Are there other ways to transfer the scheduler jobs between my 2 databases?
Thank you,
Adrian
Edited by: AdrianM on Apr 6, 2010 7:54 PM

is it JOB and SCHEDULE, my guess is schedule
if it's job, then you can use dbms_job.user_export
if it's schedule, did you try to generate DDL script instead of running the actual import and then run that DDL on a side? http://www.dba-oracle.com/job_scheduling/export_scheduler.htm

HRMS Payroll: Migrating Element Links between Environments/Instances

Hi,
I need to migrate element links between environments i.e, I need to move my element links from one instance to another.
Apart from doing this manually or using dataloader, what are the other options/best practices that I can look at?
Regards,
Santhosh Jose

We've previously done this successfully using Data Pump to process the migration of Element Types, Input Values, Extra Info and Links - once set up it works very smoothly, but it does require quite a bit of setup so I'd only advise using if you're migrating a lot of elements several times.
Data Pump is just a set of tables and concurrent programs that wrap around Oracle API's for migration of data/setup.
The setup involves getting data into these tables...
Key tables are:
hr_pump_batch_lines
hr_pump_batch_headers
hr_pump_batch_line_user_keys
Using API's like:
hrdpp_create_element_type.insert_batch_lines
hrdpp_create_element_extra_inf.insert_batch_lines
hrdpp_create_element_link.insert_batch_lines
hrdpp_create_input_value.insert_batch_lines
hrdpp_update_input_value.insert_batch_lines
Conc Program: Data Pump Engine
There should be plenty of documentation around the net and MoS about this if you want to have a read.
Alternatively you can call the API's yourself.
or, you can have a go with iSetup - we tested this briefly but didn't get too far with it, several quirky issues with loading Work Structure data so went back to using Data Pump.
Regards, Jay

Diff between database view and inner join

Hello,
I need to select data from multiple tables. I need to choose between 2 options.
1) create a database view and use this view for select.
2) write an inner join in abap prorgam.
In which cases we should create a view and in which cases we should use a inner join?
What are the factors which decide these?
Pls advice.
Thanks,
Rupali.

Hi,
Both are same..
But if you use regulary and used view in Multiple programs then create view..
If inner join in abap prorgam between two or more table used in less Programs and do not want to
create View (Means not to create transport request) then go for JOin in Program.
Prabhudas

Hi, difference between database view and elementary search help

hi
pl. can any one tell me the difference between
database view and elementary search help,
and help view and elementary search help,
and database view and help view.
in the output i do not see any difference.
thanx.
rocky robo

HI
An entire table can be included in a database view. In this case all the fields of the included table will become fields of the view (whereby you can explicitly exclude certain fields). If new fields are included in the table or existing fields are deleted, the view is automatically adjusted to this change.
Database view:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/36/74c0358373003ee10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/36/74c0358373003ee10000009b38f839/frameset.htm</a>
Elementary search help:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/8b/415d363640933fe10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/8b/415d363640933fe10000009b38f839/frameset.htm</a>
Help view:
Help views are used if a view with an outer join is needed as selection method in a search help.
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/42/81c1351181b73fe10000009b38f839/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/42/81c1351181b73fe10000009b38f839/frameset.htm</a>
Regards,
Gunasree

Difference between Database view and Table

Hi there,
Can anyone tell me the difference between Database view and Table.
Will the Database view query be more faster than a database table?

Tables and database views can be defined in the ABAP Dictionary.
These objects are created in the underlying database with this definition. Changes in the definition of a table or database view are also automatically made in the database.
Data from several tables can be combined in a meaningful way using a view (join).
You can also hide information that is of no interest to you (projection) or only display
those data records that satisfy certain conditions (selection).
Database views implement an inner join. You only get those records which have an
entry in all the tables included in the view.
in views db modifications are not possible
views only contain data at run time
when they consult the database
in case of views the join definitions are already sstored in the database itself
whereas join as open sql is a query to oracle database as similar select statements
Views are optimized by SAP and stored in the repository while Joins
are in reports that needs to be compiled at every execution
Reward if helps
Regards,
Senthil
Message was edited by: senthil kumar

Difference between Instance Crash and Database Crash in Standalone and RAC?

I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
RAC_".+
Oracle Version: 11.1.0.7.0
O.S Version: HP-UX B.11.31 U

Sivaprasad S wrote:
I am new to Oracle Environment. I would appreiciate if i get clarified on the "_+Difference between Instance Crash and Database Crash in Standalone and
RAC_".+That depends on your definitions of database crash versus instance crash.
Literally, database crash means that the database itself is damaged in some way. A disk is no more. Data files are corrupted. Etc. The database itself thus causes the crash - and a database crash will also cause all database instances (RAC or single) for that database to crash too.
An instance crash will therefore mean that the crash occurs in the instance due to an Oracle bug or similar. In other words a s/w error and not a database error. The database is still "fine", but the instance not. Instance crashes. However, any other instance on that same (RAC) database will still be fine as the database itself is unaffected by that s/w error in the crashed instance.
If you mean something different, please enlighten us. Not all crashes are equal. {noformat};-){noformat}

Diff between maintence and database views

pls answer now,its urgent

Hi
Database Views
Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.
Database views are defined in the ABAP Dictionary. A database view is automatically created in the underlying database when it is activated.
Application programs can access the data of a database view using the database interface. You can access the data in ABAP programs with both OPEN SQL and NATIVE SQL. However, the data is actually selected in the database. Since the join operation is executed in the database in this case, you can minimize the number of database accesses in this way. Database views implement an inner join (see Inner and Outer Join).
If the database view only contains a single table, the maintenance status can be used to determine if data records can also be inserted with the view. If the database view contains more than one table, you can only read the data.
Database views should be created if want to select logically connected data from different tables simultaneously. Selection with a database view is generally faster than access to individual tables. When selecting with views, you should also ensure that there are suitable indexes on the tables contained in the view.
Maintenance View:
Maintenance views offer easy ways to maintain complex application objects.
Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.
A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.
All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for maintenance views are always derived from the foreign key You cannot directly enter the join conditions as for database views.
There are some restrictions for the attributes of the foreign keys with which the tables in a maintenance view can be linked
A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data from the base tables of a maintenance view together.
Maintenance mechanisms, like screens and processing programs, must be created from the view definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-use maintenance interfaces in a simple manner.
If it is helpful rewards points
Reagards
Pratap.M

Use of non-migratable database link not allowed ERROR

Hello,
We have a notification process (on disabled user) in OIM that needs to connect to a schema in another instance to check some information before the notification is sent out.
We have OIM in an instance A and the other schema lives in the instance B. We created a database link from A to B, some synonyms, and grant the right permissions for OIM to select the tables in the schema on instance B.
We can login to OIM using SQL Developer and execute the query without any problems.
However, when the query is executed in the Disable User process task, we got the error:
java.sql.SQLException: ORA-24777: use of non-migratable database link not allowed
We tried to create a view in OIM that is similar to the one that lives in the schema in instance B. However, the same error exists.
How can we work around this error?
Thanks

with all the info you have put here all I can say is : (with some help from google ;-) )
ORA-24777: use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multi threaded server process.
Action: Perform the work in the local database or open a connection to the remote database from the client. If multi threaded server option is installed, connect to the Oracle instance through the dispatcher.

Best Practice to migrate existing Message/Central Instance to new hardware?

I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!

If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters.

Migrating database views between instances

Similar Messages

Maybe you are looking for