Submitted by sarathannapareddy on Tue, 2009-12-01 14:21
In my view, Display Manager commands didn’t get much attention of SAS programmers as they should be. It may be because...
1) SAS Documentation has very little information about how to use this facility.
2) Even Google searches aren’t helpful enough.
Here are the list of Display Manager Commands I know…
Using Manager commands we can open the dataset from any directory without touching the Explorer window…
Submitted by jp_vijaykumar on Sat, 2009-11-14 20:23
Many a time, developers ask for procedures to kill there own sessions in the oracle db.
Many of our developers are scattered around the globe in different time zones.
During on-call rotation, developers will be calling me, round the clock, to kill their sessions.
Submitted by David Lozano Lucas on Fri, 2009-10-23 06:30
Here I present a simple query to use when we want to move the tables and indexes of several users at once.
To make it one by one:
ALTER TABLE xxxxxx MOVE TABLESPACE TEST;
ALTER INDEX xxxxxx REBUILD TABLESPACE TEST;
To move data from multiple owners. In this example OWNER1 and OWNER2:
Submitted by mjshank on Mon, 2009-10-19 20:05
Just testing things a bit. Sorry if you got spammed with this bog entry. I am posting at both OraFAQ and Oracle forums to try out the two interfaces for blog entries. Also trying blogspot.com and Google Sites.
If you have tried out the blogging and have a preference for one vs another, please let me know.
Submitted by David Lozano Lucas on Tue, 2009-10-13 09:06
It is an English word that sounds very funny in Spanish, almost unreal.
Well, just wanted to brand the blog with a first entry to introduce myself.
I work as an Oracle and SQL Server DBA (mixed profile, they call it -
concerns twice for the same pay, on me).
Here I will write "how to" articles as they emerge in my day to day.
If you can read Spanish, check out the blog I maintain for a little more time http://blog.davidlozanolucas.com/.
Submitted by Kevin Meade on Fri, 2009-10-02 11:59
I saw one of those really interesting pieces of code recently. A guy wanted to run his transaction and make it fail when it was all done. Normally one would put ROLLBACK at the end of the transaction in order to undo a transaction's work. But this guy did not want to do that. He wanted to keep his transaction code unchanged, commit at the end and everything. He had several reasons for this, among them being that he did not have access to all the code he was working with and thus could not put the ROLLBACK where it was needed, and indeed suspected (as we eventually found to be true), that somewhere in the code stream there was a commit being done without his permission thus splitting his transaction in ways he did not intend. So he wanted a way to FOREORDAIN (determine ahead of time) that his transaction would fail no matter even if it went to conclusion without error. For this he came up with a I think a clever hack. Seems to me this might have some use, if I can figure out what that use might be. So here is the cool solution.
Submitted by Kevin Meade on Wed, 2009-09-30 12:38
Recently a friend asked me for this. I see it a lot on OraFaq as a question in the forums so here are the basics of working with delimited strings. I will show the various common methods for creating them and for unpacking them. Its not like I invented this stuff so I will also post some links for additional reading.
Submitted by Kevin Meade on Sat, 2009-09-26 23:34
Star Schemas are proliferating with warehouses these days. Many practitioners I have met in this space are a bit new to the concept of star schemas and as such keep falling back to old habits. But this is only hurting them. So I'll try to give my simplistic view of how it works in the hopes of granting some clarity on the practice of Star Modeling and overcoming our previous training to resist its concepts.
Submitted by akgc2 on Tue, 2009-09-15 04:28
You might face a situation where you need to interchange the values of two columns in an Oracle database table. This article will explore ways to achieve this.
Submitted by purple73 on Sat, 2009-08-29 20:30
During a quite evening of my last on-call bout I was alerted from our monitors that the UNDO tablespace was running out of free space. Thought of adding of a new data file and be done with it; When I checked the current allocation for this tablespace it was already at 40G - couldn't believe what I was seeing. The undo_retention was set to 7200 and max query length in v$undostat was not that high. One column that did caught my eye was the tuned_undoretention, its value was way very high.