Moving of EUL from Prod to Replicated Database

Hi All,
I have a question, I have to move EUL from PROD Database to the Replicated Database for good, can i do that in R12? version of the ebiz is 12.1.3 and Discovers EUL has to be moved I know it is quite tightly integrated. Is there a way to perform this task. Your comment and view are Appreciated
Regards
Younus

Ah, that old "dynamically". Which means "Some mysterious process which is too complicated for me to understand", at least that's how it's commonly used in Java language forums.
But it isn't really that mysterious. Given a table, run the query "select * from table". Then use the ResultSetMetaData to find out how many columns you selected. Then create an insert command with that many parameters and build a PreparedStatement from it. For each row in the ResultSet, copy its columns to those parameters and execute the insert.
Or you could use the database's own features to do the copying. Probably more practical than writing "dynamic" Java code anyway.

Similar Messages

Moving Exchange 2010 Mailbox replicated databases path in DAG environments.

Hi there,
I’m trying to get some feedback on the topic of moving Exchange 2010 Mailbox replicated databases path in DAG environments.
Here is the situation: I currently have a 3-Node DAG (Node 1 and Node 2 are in my main datacenter, and Node 3 in my Disaster Recovery (DR) site in a remote location.
I have DB copies in Node 2 and Node 3. The thing is that the DB copies in Node 2 are in an older storage box and since we got a new storage box, I need to move the DBs and related logs of Node 2 to the new storage box
I have found some information about how to deal with this (below I’m listing a KB link) but I would like to reconfirm a couple of things to make sure I’m understanding this correctly
Move the Mailbox Database Path for a Mailbox Database Copy:
https://technet.microsoft.com/en-us/library/dd979782%28v=exchg.141%29.aspx
According to the KB: “If the mailbox database being moved is replicated to one or more mailbox database copies, you must follow the procedure in this topic to move the mailbox
database path”
Would this apply to my case even when I’m moving the BDs copies and Logs on Node 2 as opposed to Node 1 where the source DBs are?
On step #3 in the procedure, you are supposed to “Remove all mailbox database copies for the database being moved. After all copies are removed, preserve the database and transaction log files from each server from which the database copy is being removed
by moving them to another location. These files are being preserved so the database copies do not require re-seeding after they have been re-added.”
Then in Step # 7, you are supposed to “Add all of the database copies that were removed in Step #3”
As far as I know, when you add a copy of a database, Exchange creates the copy DB and starts to seed the replica servers with an up to date copy of the DB and all the current transaction logs at that point…according to the instructions
above, you are supposed to re-add the DB copied we preserved...does it mean that we need to wait for the DBs seed process to finish after “adding the DB copy” and then replace the new DBs copies and logs created by the “Add database copy” function with the
DB and logs preserved in Step #3?
Thanks in advance for your feedback!
FT
FT

Hi there,
What the article is stating is that once you have removed the copies you can keep the existing transaction log files and database edb file to allow you not to have to do a full seed. You can do this by using the -seedingpostponed parameter in
Add-MailboxDatabaseCopy
However, and quite honestly, if your database isn't that big and your are not worried about performing a full copy of the database again to the other DAG members once you have moved your database to its preferred new location, just add the copy in the normal
way and remove the legacy files afterwards.
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Checks to be done before moving the objects from DEvV to PROD systems

Hi,
Please provide the standard methods and checks to be done in the transport requests before moving the objects from DEv to PROD.
Please help us here.

In se10 find your request and
Upper left corner - Request\task -> Complete check -> Object (syntax check) and Check Request Consistency.
This you can do for your request and all the tasks included in your request.
Note: Transport may still fail due to numerous reason (i.e) not all the objects needed are collected in the request,
but at atleast it gives some assurance that objects are not blocked in other requests etc...

Best way to update DR database from PROD server automatic ?

Hello Gurus,
I want to decide best solution.
Goal: Best way to update DR Database from PROD Server Database automatic.
System: 32 bit Linux system with Oracle Database 10g Release 10.2.0.4.0 - Production (database version) Oracle version is standard.
Please let me know how i can update my DR server with PROD data and this task should be automatic.
Please ask me more information if required to solve this issue.
Thanks- Priyank
Edited by: Oracle DBA P on Nov 19, 2010 3:06 AM

you mean to say data guard needs to implement ? i think that's one option but what you said is different ?
tell me procedure how i can implement your idea ? steps i have to perform.
Thanks
Edited by: Oracle DBA P on Nov 19, 2010 3:38 AM

Help in refrshing TEST from PROD database

Hi All,
I need to refresh one of my test server with Production instance from the cold backup.
Please post a detailed steps i need to perform to do this.
Both of databases are in different servers and both are windows servers.
Appreciate helping me to learn.
Regards
Arun

Hi, are you sharing storage between the prod an test database?
If not, why dou want to rename the datafiles?
However, if you want to rename the datafiles, you have to change the datafiles name at S.O. level (I suggest you to copy -duplicate- the datafiles and, once you have renamedthe datafiles and checked that the database works fine, then delete the "old" datafiles).
I don't suggest you to rename system's datafile! (But internet is full of procedures for do it)
For change datafiles names at dabase level (ergo, at logical level) you have to do the following:
startup mount;
and, for each datafile:
alter database rename file 'old_name' to 'new_name';
You can check the old names, and your progress querying the v$datafile view.
I hope this help.
Regards.

Moving audit Records from one database to another database using dblink

i got five database, i have to move sys.aud$ records from five databases to one centralized database into another schema every day at 10:00 clock, i have to use a dblink for this, i have to create same table as sys.aud$ with different schema in centralized database with one extra column db_unique_name,by using db_link how i need to move records from all the five databases to one centralized database, can anyone help me here how to create a db_link from to move records from five database to one centralized database, due to maintainance perspective i have to move the records from all the five databases to one centralized database. i have to write a script for moving the audit records from all the five databases to one centralized database, can anyone help me how to write the script, or if you have any related scripts , can u post here, it will helpful for me.

spool audit.log
--"Auditing Initialisation Parameters: check initialization parameter"
select name || '=' || value from v$parameter where name like '%audit%'
---"if auditing is disabled then issue this command and bounce"
alter system set audit_trail=db,extended scope = spfile
shutdown immediate
startup
create tablespace ORDER_DATA datafile '+DDATA' size 50m;
create user INFO identified by INFO;
Grant connect,resource to INFO;
Alter user INFO quota unlimited on ORDER_DATA;
create table INFO.ORDER as select * from sys.aud$;
alter INFO.ORDER add db_unique_name varchar2(50);
create table INFO.ORDER
partition by range (Timestamp#)
subpartition by hash(dbid)
subpartition template
(subpartition sp1 tablespace users,
subpartition sp2 tablespace users)(
partition p1 values less than (TO_DATE('07/29/2010','MM/DD/YYYY')),
partition p2 values less than (TO_DATE('07/29/2011','MM/DD/YYYY')),
partition p3 values less than (MAXVALUE)) tablespace BGORDER_DATA as select * from sys.aud$
spool off;
exit
BEGIN
DBMS_SCHEDULER.create_job(
job_name => 'Move Aud$ records',
job_type => 'PLSQL_BLOCK',
job_action => 'CREATE OR REPLACE PROCEDURE bgorder_aud
                    AS
               ts TIMESTAMP;
               BEGIN
ts := SYSTIMESTAMP;
insert into info.order select * from sys.aud$ where timestamp# < ts;
delete sys.aud$ where timestamp# < ts;
commit;
END;
start_date => TRUNC(SYSDATE) + 22 / 24,
repeat_interval => 'FREQ=daily;BYHOUR=22;BYMINUTE=0;BYSECOND=0',
enabled => TRUE,
comments => 'Move records');
END;
/

Duplicate database from prod environment to test environment.

hi,
Am trying to Duplicate the database from Production RAC Envrionment to Test RAC Environment.
Am following the metakink Document: How To Restore Rman Backups On A Different Node When The Directory Structures Are Different [ID 419137.1]
When am restoring the backup from prod in Test environment am getting the following error.
ORA-19870: error reading backup piece /rman2/stage/backup_of_PROD_21047_07_04_2011_1
ORA-19504: failed to create file "+DG1"
ORA-17502: ksfdcre:4 Failed to create file +DG1
ORA-15055: unable to connect to ASM instance
ORA-00020: maximum number of processes () exceeded
ORA-15055: unable to connect to ASM instance
ORA-00020: maximum number of processes () exceeded
Please help me out in this.
with regards
A.Aravind

Pl post details of OS and database versions on the source and target.
RMAN Duplicate Failing With ORA-19870 ORA-19504 ORA-15012 ORA-17502 ORA-15080 (Doc ID 417074.1)
Srini

Moving data from .xls spreadsheet to database table

Hi,
Does any one know a script or the procedure to move data from an .xls spreadsheet to a database table?
Thanks,
Ranjana

Hi,
check this out.. !!
Import data from Excel to Oracle Database and
Added link From Ask Tom.. your requirement you would be satisfied.. I supppose.. !!
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:908428873069
- Pavan Kumar N

Insert or Update data from PROD dc to DEV DB

We have one instance of a DB in PROD box and another in DEV box [unix]
Requirement is to write a script to copy data from PROD to DEV for 10 related tables.
Store Procedure will have input argument as Number or FromDt and To Date [date range]
Can anyone give step by step guide to do this? Have worked on Package proc and store proc for Oracle 8 but for long have no touch or Oracle. We have Oracle 10g at present.
TIA.

"@PROD" uses a database link (called PROD) to access the remote table. In the definition of the database link are all the sql*net parameters necessary for one database to connect to another.
You can start by reading the SQL Reference Manual to get the basics of the CREATE DATABASE LINK statement. It has links to other manuals as well:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5005.htm#i2061505

Moving the log file of a publisher database SQL Server 2008

There are many threads on this here. Most of them not at all helpful and some of them wrong. Thus a fresh post.
This post regards SQL Server 2008 (10.0.5841)
The PUBLISHER database primary log file which is currently of 3 blocks and not extendable,
must be moved as the LUN is going away.
The database has several TB of data and a large number of push transactional replications as well as a couple of bi-directional replications.
While the primary log file is active, it is almost never (if ever) used due to its small fixed size.
We are in the 20,000 TPS range at peak (according to perfmon). This is a non-trivial installation.
This means that
backup/restore is not even a remotely viable option (it never is in the real world)
downtime minimization is critical - measured in minutes or less.
dismantling and recreating the replications is doable, but I have to say, I have zero trust in the script writer to generate accurate scripts. Many of these replications were originally set up in older versions of SQL Server and have come along for the
ride as upgrades have occurred. I consider scripting everything and dismantling the whole lot pretty high risk. In any case, I do not want to have to reinitialize any replications as this takes, effectively, an eternity.
Possible solution:
The only option I can think of is to wind down everything, such that there are zero outstanding uncommitted transactions and detach the database, delete the offending log file and reattach using the CREATE DATABASE xyz ATTACH_REBUILD_LOG option.
This should, if I have understood things correctly, cause SQL Server to recreate the default log file in the same directory as the .mdf file. I am not sure what will happen to the secondary log file which is not moving anywhere at this point.
The hard bit is insuring that every transaction in the active log files have been replicated before shutdown. This is probably doable. I do not know how to manually flush any left over transactions to replication. I expect if I shut down all "real"
activity and wait for a certain amount of time, eventually all the replications will show "No replicated transactions are available" and then I would be good to go.
Hillary, if you happen to be there, comments appreciated.

Hi Philip
you should try this long back suggested way of stopping replication and restore db and rename or detach attach
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6731803b-3efa-4820-a303-4ffb7edf154a/detaching-a-replicated-database?forum=sqlreplication
Thanks
Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem
I do not wish to be rude, but which part of the OP didn't you understand?
Specifically the bit about 20,000 transactions a second and database size of several TB. Do you have any concept whatsoever of what this means? I will answer for you, "no, you are clueless" as your answer clearly shows.
Stop wasting bandwidth by proposing pointless and wrong solutions which indicate that you did not read the OP, or do you just do this to generate points?
Also, you clearly failed to notice that I was on the thread to which you referred, and I had some pointed comments to make. This thread was an attempt to garner some input for an alternative proposal.

Moving SQL servers from one Protection group to another

We are using DPM 2012 R2 Update Rollup 4. We have started to move some SQL servers from a Protection group with 90 days of retention to a Protection group with 15 days of retention. The recovery data is co-located on the backup device and we are using
disk based backup. A couple days after moving a couple of the servers, I have noticed that the number of recovery points has stayed the same and not decreased. It would seem that when moving to a different protection group, that the SQL server
would inherit the new retention settings instead of retaining the ones from the old protection group. When I moved them, I stop protection of the databases and then added them to the new group. Why is this occurring and how do I get the new retention
settings in the new protection group to take affect?

Thanks for the information. DPM is really a pain when trying to move co-located data sources to different protection groups. I do hope in future versions that this is simplified and corrected. I am now stuck for 90 days with data that I
don't want and I can't get rid of without getting rid of every recovery point for that group. That is bad news when my LDM DB is almost full.
An important note for those who are trying to see how many extents certain data sources have when following this article
http://blogs.technet.com/b/dpm/archive/2010/03/30/what-volume-to-migrate-first.aspx
If your DPM DB has changed from "DPMDB" to DPMDB with bunch of random characters, you will need to this line in the script for it to work.
$db = $srvr.Databases["DPMDB"]
<-- change this to your server’s DPMDB name
Also, you will need to greatly increase the width of your command window to see the "NumberOfExtents" column which is the most important column.

Move Business Area and EUL from one schema to another

Hi,
I need to take a EUL from the schema where it is now and bring it to another schema. I use Oracle Discoverer 3.1 Admin Edition to Export Business Area then import it in the new schema. Everything works fine except the fact that workbooks (.dis file) created in the original schema returns no data (as it does in the original schema).
Anybody can help ?

Hi,
There could be a number of reasons for this, but the first thing to check is whether Discoverer is generating the same SQL when the report is run in the two EULs.
If the SQL is the same Discoverer could still return different data if for example there were user specific conditions in the query or language specific conditions in the query and the default language was different in the EULs.
Are you using an Apps or database mode EUL? What is in the workbook query that you are running?
Rod West

UAT DB's nonsystem dfile corrupted. how can I restore it from Prod by rman

I have an UAT env. some non system tablespace's datafile corrupted (one tb one dbfile)
errors look like below and the db could just be in mount state.
Database mounted.
ORA-01157: cannot identify/lock data file 4 – see DBWR trace file
ORA-01110: data file 4: ‘D:\ORACLE_DATA\DATAFILES\ORCL\USERS01.DBF’
When I took them offline, the db could be open.
I could not use rman to recover it although it is in archivelog mode. it is because some corruptions in archived logs.
Now, I would like to recover them from prod db.
How can I do that by using rman/ export import. My DB's version is 10g R2
I appreciate if there are any reference and instructions from all of you.
Many Thanks

you can use data pump export/import instead of traditional exp/imp, if you are oracle 10g or high. These tools are much faster(approximately 10 times) than traditional exp/imp.
There is also another possibility you can use, which is called transportable tablespaces. Of course it will not be convenient if your corrupted datafile is one of the several datafiles of the certaion tablespace. But if your tablespace just consists of this corrupted datafile, you can use this method, which is much faster than export import tools.

Moving a system from MSSQL 2000 to MSSQL 2000 IA64

Hi
We have a R/3 Enterprise 47x110 system running on MSSQL 2000/windows 32 bit. We want to change our hardware to 64 bit. According to platform availability matrix, we have to use mssql 2000 ia64/win2003 ia64 with this release. We want to know which procedure has to be used for moving a system from mssql 2000 32 bit to mssql 2000 ia64?

Hello
Migrating an SAP system from Windows SQL IA32 to Windows SQL IA64 is a fairly simple procedure.
I have performed this migration myself several times.
You need to ensure that your source system (IA32) has the required support pack levels for SQL 2005
I recommend you review 905634, 151603 and 683447.
I would strongly recommend that you move directly to SQL 2005 rather than SQL 2000. SQL 2005 is fully supported and offers a lot of performance and administration features (such as snapshots).
SQL Data files are compatible between SQL platforms. By this I mean if you do an sp_detach on an SQL IA32 system you can sp_attach them to an SQL IA64 system without any special action. The files are also compatible between SQL versions, you can detach from SQL 2000 and attach to SQL 2005. This is described in section III of 799058.
In your case I would:
1. Make sure you support packs are up to date on source system
2. Make sure you are using the correct collation 600027
3. Install 4.7 on your IA64 host from the install CDs
4. Update your IA64 system kernel to the correct level
5. Detach the "empty" DB from the IA64 host
6. Shutdown your IA32 system, stop SQL, start SQL and then stop SQL
7. Copy the datafiles and log files to the IA64 system
8. Attach them to your IA64 SQL 2005 system
9. Run the SQL Tools utility
10. Start up your 4.7 instance
11. Check SM21, ST04, SICK and DB02
12. Reschedule your backups and DBCC
This procedure should work and should be quite simple to implement. You can leave you IA32 system untouched, so if you experience any problems you have a fall back position (ie. just restart your IA32 system - nothing has changed on you IA32 system or its database).
I recommend you obtain the official SAP SQL 2005 CD, it includes SP1 and has a useful script call SQL4SAP.VBS that sets a lot of options for you automatically.
Check 879941 - you may need to adjust the torn page setting and auto_update_statistics_async settings or you will get red alerts in your CCMS tree.
For other people out there who use Java systems (EP, XI etc) you <b>will almost certainly</b> have to update your JDBC drivers. See note 639702.
Hope this helps, let me know if you have any questions.
Goodluck
Message was edited by: Sam Badan

Migrate DRM application from PROD to TEST environment

How I can migrate all DRM application from PROD to TEST environment. The first way this is using migrate utility and then create all export/import utility. But this way does not give 100% guaranty of identity the PROD and TEST environment.
As relation database I am using Oracle DB. Can I migrate DRM application using exp/imp utility for oracle users (MDM and MDM_DB) and after that changing information directly in oracle tables in the TEST environment?

This response is not timely but others may find it useful...
You can use the Oracle database export and import processes, but there are several additional steps in the process. In general this is a high risk endevour that should not be attempted by the faint of heart. (See #3 below!) Attempt at your own peril.
1) Make a copy of the Username table so that you have the Test versions of the encrypted passwords for DRM internally managed accounts. These will need to be updated post import if there are any differences.
2) After you delete the tables in Test, it's best to create them with the install scripts prior to import because once an Oracle table containing a blob datatype has a stored value the Oracle import is no longer tolerant of changes in target tablespace names for all tables containing blobs within that schema. (Known bug) However, the create tables install script has an insert statement or two that need to be commented out or the import will create duplicate rows that will cause errors enabling constraints.
3) After the import completes all exports and books need to be modified to no longer point to production target locations, especially for exports to database tables! Ideally this step would be completed and QA'd prior to starting the application server; however, the application server must be running if the migration utility is going to be leveraged to propagate these updates so the process I use is to lockout all users until this step is completed.
4) Also note that if the Prod and Test app servers are not using the same authentication settings the system preference needs to be changed or the application server may not start.

Moving of EUL from Prod to Replicated Database

Similar Messages

Maybe you are looking for