I was think what about only for queries and useful functions, excluding scripts (i.e. for upgrading, installing, etc.) one example A query to get the current execution of a user and the value of the binding I took me some hours to make it. if some one could improve it will be nice. The question is who will take the responsability of the repository. SELECT LAST_LOAD_TIME,(SELECT MAX(TO_CHAR(S2.LOGON_TIME,'HH24:MI')||'-'||SUBSTR(S2.STATUS,1,3)||'-'|| S2.username||'-'||S2.osuser||'||'||S2.TERMINAL ||'-'|| S2.program||'||'||S2.module||'||'||S2.action||':logon_time:'||TO_CHAR(S2.logon_time,'DDMONYYYY HH24:MM:SS')) FROM V$SESSION S2 WHERE S2.SID=S.SID AND S2.SERIAL#=S.SERIAL#) IDENTIFICACION, SQL_TEXT, SQL_FULLTEXT,FIRST_LOAD_TIME, 'SELECT * FROM V$SQL_BIND_CAPTURE WHERE HASH_VALUE='''||T.HASH_VALUE||''' AND CHILD_ADDRESS='''||T.CHILD_ADDRESS|| ''''||CHR(59) BINDS,S.USERNAME,S.SID, S.SERIAL# FROM V$SESSION S, V$SQL T WHERE S.SQL_ID IS NOT NULL AND S.SQL_ID = T.SQL_ID ORDER BY LAST_LOAD_TIME desc 2014-06-11 11:03 GMT-04:00 Ethan Post <post.ethan@xxxxxxxxx>: > My direction towards scripts over the years has been fewer is better. > Instead of multiple lock scripts for example, just wrap them all into one. > I would rather get a big .txt file with a lot of information which I can > easily page through to find the issue than to have to run multiple scripts. > This lends itself to easier automation in terms of "alert trigger" then run > "diagnostic script" type of responses. Also I lean towards including as > much context and historical information in the scripts. > > Agree that GitHub would be good for this. Would like to see some high > standards however and not just save everything here sort of thing. Of > course this is easy to say since I won't be doing it right :) This can > lead to a lot to a lot of dead branches however as folks will fork if they > don't like the rules. One downside perhaps. > > With respect, > EP > > > On Wed, Jun 11, 2014 at 6:56 AM, Jeremy Schneider < > jeremy.schneider@xxxxxxxxxxxxxx> wrote: > >> How in the world did I forget Morgan's Library? I'll add that once I'm >> sitting down at a computer! >> >> -- >> http://about.me/jeremy_schneider >> Sent from my iPhone >> >> On Jun 10, 2014, at 6:52 PM, Juan Carlos Reyes Pacheco < >> jcdrpllist@xxxxxxxxx> wrote: >> >> Very nice Jeremy :), >> I was thinking in this idea but I'm not sure how reliable it is. >> The idea I was thinking some was about a shared repository, most sites >> has script in example http://psoug.org/browse.htm?cid=4, but there is >> not something more ordered. >> In different levels >> 1) common functions >> One example is a package having all numeric functions or date functions >> oracle hasn't. >> 2) Useful queries >> How to get the sql one session is executing and how to find their bindings >> 3) specific scripts for specific tasks >> in example how to export in oracle 7 to Oracle 8i from linux to Oracle >> 4) The most important how to get easy to search and get Oracle people use >> them. >> >> Maybe this could be only for oracle-l list, some one should have the task >> to update, but the amount of scripts and task in Oracle are too much. >> But at the same time the fact there are so much task, causes the need of >> having a library of script, wrote by people with experience. >> >> In conclusion it is a dilemma :) >> >> >> >> 2014-06-10 10:18 GMT-04:00 Jeremy Schneider < >> jeremy.schneider@xxxxxxxxxxxxxx>: >> >>> I made a list of dba script collections from oracle-l a few months ago, >>> the list was included here: >>> http://ardentperf.com/2014/01/02/novemberdecember-highlights/ >>> >>> That originated from an old thread on this list: >>> //www.freelists.org/post/oracle-l/best-DBA-script-collection >>> >>> It would be *great* to get some of this stuff on githhub, if only for >>> the ease of forking and tweaking and merging. (Tanel are you going to put >>> your stuff on there sometime? <g>) >>> >>> -Jeremy >>> >>> >>> -- >>> http://about.me/jeremy_schneider >>> >>> >>> On Mon, Jun 9, 2014 at 6:55 PM, Juan Carlos Reyes Pacheco < >>> jcdrpllist@xxxxxxxxx> wrote: >>> >>>> I'm not sure about maintenance, I think the idea is to store what you >>>> have by database release. >>>> >>>> This is not only the script is the idea you can do that. >>>> >>>> The other idea was to create a schema to install, having the basic >>>> functionality everyone needs like useres, security, instrumentation ,etc. >>>> >>>> Thank you for answering. >>>> >>>> >>>> 2014-06-06 13:06 GMT-04:00 David Fitzjarrell <oratune@xxxxxxxxx>: >>>> >>>> This sounds like a good idea in principle; the maintenance of these >>>>> scripts might be an issue, however. >>>>> >>>>> I do find it helpful to see scripts from other DBAs to see what >>>>> they've done and see if I can find something I can use without >>>>> re-inventing >>>>> the wheel. >>>>> >>>>> David Fitzjarrell >>>>> Principal author, "Oracle Exadata Survival Guide" >>>>> >>>>> >>>>> On Friday, June 6, 2014 10:19 AM, Jared Still <jkstill@xxxxxxxxx> >>>>> wrote: >>>>> >>>>> >>>>> >>>>> On Thu, Jun 5, 2014 at 4:45 PM, Juan Carlos Reyes Pacheco < >>>>> jcdrpllist@xxxxxxxxx> wrote: >>>>> >>>>> Of course someone must be on charge of updating. It will be a lot of >>>>> work but I think this can be very useful. because there will be stored by >>>>> Oracle release and edition, and this can be very help full. >>>>> >>>>> >>>>> The current best choice for that would probably be a publicly >>>>> accessible (default) github repo. >>>>> >>>>> >>>>> Jared Still >>>>> Certifiable Oracle DBA and Part Time Perl Evangelist >>>>> Sr Oracle DBA at Pythian >>>>> Pythian Blog http://www.pythian.com/blog/author/still/ >>>>> Oracle Blog: http://jkstill.blogspot.com >>>>> Home Page: http://jaredstill.com >>>>> >>>>> >>>>> >>>> >>> >> >