browse by category or date

Today I was required to copy some data from our production Oracle server into test server. To do the schema & data transfer, I used Oracle SQL Developer. I am assuming that the connections to both production and test servers is already added in SQL Developer.

In SQL Developer, select Tools -> Database Copy

Next, select the source (Production) and destination (Test) database. In my case, the production server is TMS, and the test server is TMS ES4. Also select the “Schemas Copy”.

Next, select the object types to copy over. By default all object types will be selected.

Next, select the schema to copy. Here in my example, actually all schemas exist in my production DB are shown. I only needed one schema, RICHLAND.

Next, we select the objects within this schema to be copied over. Click the “Lookup” button to show the objects, then include objects that you want. For my case, I clicked the >> button to select all objects.

Next, we select which data to copy over. You can add conditions to each table to ensure you copy the correct data.

Last step, the summary of the process will be shown. If you realize any mistake, you can always press “Back” button to correct it.

Click “Finish”, and the copying process will start.

That’s all 😀 If you encounter any issues, drop a comment at the bottom of this page.

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

Last night derby game was excellent. United able to maintain their winning streak by overpowering City. United now can concentrate aiming for Top 2 while City need to fight for Top 4. Considering that City lost 6 in their last 8 games, City really really need to get their things right immediately.

I must admit, United started last night game slightly nervous. It was City who came close first. At 5″, Demichelis clearance set free Jesus Navas. Navas racing alone with Daley Blind helplessly chasing him. Great positioning by David De Gea as Navas’ shot went straight to De Gea legs.

City went up at 8″. United’s defence was asleep allowing David Silva unmarked inside the box. Silva squared the ball for simple tap by Sergio Aguero. My heart immediately sank thinking that going down within the first 10 minutes will dent United’s confidence.

Luckily, United didn’t easily bow down to City. United levelled at 14″. It was started from a sloppy back-pass from Phil Jones. The ball was not fast enough with Navas blazingly closing down. Thank God De Gea managed to frantically clear the ball before Aguero get a touch. The ball was hoofed far in City’s area before bouncing off Marouane Fellaini into Ander Herrera’s feet. Herrera then crossed the ball into the box. Gael Clichy slid trying to clear, but the ball fell nicely in front of in-mid-rotation Ashley Young. Young able to balance himself before smashing the ball into the net. The whole Old Trafford breathed a sigh of relief!

With the scores level, United switched into controlling mode while City fell apart. At 26″ United take lead courtesy of Fellaini’s header. A nice teamwork on the left between Blind and Young take the focus from City’s defence leaving Fellaini relatively unmarked on the right. Young then crossed the ball to the unmarked Fellaini. Fellaini then headed the ball into the net. It was poor awareness for Clichy. He is supposed to guard Fellaini was too late to realize it. Then again, he is definitely will not win against Fellaini in air battle.

Three minutes before the break Vincent Kompany lunged at Blind. The referee gave him yellow card with United fans all booing him thinking that it should have been red. City was lucky to still play with 11 players.

The second half start with Eliaquim Mangala came into the pitch replacing the limping Kompany. Can Mangala marshall City’s defence and prevent more goals conceded?

Apparently not. In a quick counter-attack, Fellaini wins back the ball, then pass it to Blind. Blind quickly pass to Rooney. Rooney then sets free a possibly offside Juan Mata. Mata kept on running one-on-one against Joe Hart. He then coolly slot the ball between Hart’s legs. GOALLL!! United lead by 3 to 1. On the replay, it was clear that Mata was offside, even-though the flag stays down.

What a defending mess from City. Seven minutes after the last goal, United increased the tally. Youngs’s free kick from the left met with Chris Smalling’s powerful header. It looks like another case of offside. But upon closer examination, it was Mangala who kept United players on-side.

It’s really game over for City. Although Aguero scored another goal at 89″, they didn’t celebrate as they know they can’t save the sinking ship.

Glory Glory Man United. Bring it on, Chelsea 😀

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

Google ChromeWhenever I tinkered with this blog, I always view the result through Google Chrome’s Developer Tools Console to see any errors. Today I realized I found one error.

And this is the offending line (prettified into multiple lines):

<link 
	rel='stylesheet' 
	id='open-sans-css'  
	href='//fonts.googleapis.com/css' 
	type='text/css' 
	media='all' 
/>

Problem is, the url is invalid. If we open the url //fonts.googleapis.com/css, Google will serve an error page.

My first reaction to this was view my WordPress theme’s source code. Nothing. The next suspect would be my WordPress plugins. I used Notepad++ to help me scouring my WordPress local copy.

It found nothing. If it’s not my theme, or my plugins, then I should be WordPress itself that added the offending line. To prove it, I searched it in my website’s root directory.

grep --include=\*.php -rnw . -e "open-sans-css"

Still found nothing. Then out of curiosity, I viewed the source code in Firefox. Surprise! The offending line is not there! It was Google Chrome itself who added the offending line. FYI, I’m using the latest Chrome version.

Now that we know the culprit, the next question is why. Why would Chrome added this line? I kinda think that Google wants to add a standardized web-font, making sure that any website that use open-sans font will have the same look in all Chrome browser.

What do you think?

PS: I’ve reported this issue to Google.

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant: