Home » Other » Test » Forum update
Forum update [message #506180] Fri, 06 May 2011 19:55 Go to next message
BlackSwan
Messages: 26722
Registered: January 2009
Location: SoCal
Senior Member
OraFAQ Forum Guide


Introduction

Welcome to OraFAQ Forum! Please, read this document before you start to actively participate. Here are guidelines of how to behave on the Forum in order to make it a cozy place to stay.

Some of the most important instructions are:

  • Be polite!
  • Never belittle anyone for asking beginner-level questions or for their English skills.
  • Use English language in the main forum (non-English forums are also provided - see bottom of list) and DO NOT use IM-speak!
  • Provide all relevant information about your problem, including Oracle software version (4 decimal places) and operating system version.
  • Format your code and make sure that lines do not exceed 80 characters. Use the "Preview Message" button to check it.

Click on a section title to expand its text.
Posting guidelines

Theory

  • Have the courtesy to write in plain English; it is not the first language of most of the participants to this forum, but that is no excuse for poor or non-existent punctuation.

    • If everyone used standard punctuation, like spaces between words and sentences, capitals for the first word of a sentence, a full-stop (period) to mark the end of a statement or a question mark to terminate a question then your requests will be more easily understood and your questions answered more clearly and quickly. Got it? Try it, it isn't that hard.

    • Also, stop putting every phrase in a new paragraph, it makes entries deep and hard to read.

  • People don't feel encouraged when they have to decipher some gobbledygook.

    Abbreviations like "U", "Ur", "U r", "Plz", "prb", "qry" especially tend to get on people's nerves.
    IM speak
    is not appreciated:
    • It is hard to read.
    • It is unprofessional.
    • It doesn't show much respect towards your fellow forum members.

    If you don't take time to write in proper English, how can you expect that others would answer properly?
  • Always spell check and proof read your messages before posting them.
  • As a rule of thumb: be polite. No one is paid for answering your question. The least you can do is show some respect to those who are willing to dedicate some of their spare time to look at your problem.
  • If you feel that a message is not admissible for some reason (offending language/opinions, personal attacks, ...), you can report it to the moderator staff. But if you want extra attention for your topic, reporting will act counter-productive.
  • Don't use uppercase only. It's harder to read and gives the impression you're shouting.
  • Choose a topic title that makes sense & clearly states problem to be solved.
    A good title might be "ORA-1555 during pl/sql loop"
    Do NOT use a single word title like "Query", "export", "SQL", etc.
    Do NOT use a two word title like "Slow Query", "Need Help", "Got Error", "SQL Plus", etc.
    A less fortunate choice might be "URGNT PLZ!!!!!!!!!!!!"

    Avoid the following keywords: urgent/please/help/now/immediately (and derivatives)
  • Choose the appropriate forum. If in doubt, don't worry - moderators can always move it
  • Don't cross-post. Duplicates will be removed.
  • Commercial posts are admitted only in the Marketplace Forum.
    • As a corollary, do not post a link to your site or blog unless it answers the question.


Practice

  • Post Operating System (OS) name & version for DB server system.
  • Post results for Oracle RDBMS by invoking following SQL
    SELECT * from v$version
  • By doing so, you'll avoid reactions using features you can't use.
  • Post details about virtualization; Base OS name & version, guest OS name & version, and name & version Virtual Machine s/w
  • Show us what you did (if you tried it yourself) and how Oracle responded (COPY & PASTE your SQL*Plus session), including errors and/or why the result is not what you want.
    Do not describe, explain or report - show us!
    Do NOT post "procedure does not work" or "results is not correct".
    While statement above is undoubtedly true for you, it is 100% devoid of actionable details.
    Post using COPY & PASTE what you do & complete results.
    Explain why the posted results are not as desired.
    Post expected & desired results & explain why it is correct.
  • Provide DDL (CREATE TABLE, etc.) as appropriate instead of listing the table structure. It'll help people setting up a test set (yes, some people really do that)
  • Provide INSERT statements for sample data instead of pasting in or mocking up the results of a SELECT statement.
  • Provide your expected result set and explain the rules/reasons that lead to it.
  • If you want to post error codes or SQL*Plus output, just copy everything that is on your screen when the error occurred, for instance:

    SQL> insert into t2 values (t2_s.nextval, x1) returning id into :x2;
    insert into t2 values (t2_s.nextval, x1) returning id into :x2
    *
    ERROR at line 1:
    ORA-00984: column not allowed here


  • Do not describe your problem and/or solution in MS Office Word, Excel, *.pdf, *jpg or similar files and attach them to your message. Some people can not, some do not want to download them. Plain TXT files are acceptable.
  • Be patient. A lot of people here are just browsing the board once a day.
  • Don't think you have more chance if you PM individual members. Just post your question in public: more people can see/answer them that way. Most PM'ed questions are posted to the forum anyway.
  • Again, forum members are not here to do your work for you nor to do your homework assignment for you. If you are stuck, we will gladly help you out.
  • Don't "wild post", i.e. post a reply that has nothing to do with the original thread.
  • If you found an answer yourself, post it. That way we know the issue is resolved and we might learn from it.


How to get a quick answer to your question?

Useful sites

How to format your post?

Responding to Posts

Performance Tuning

All about braindumps

Marketplace

You have an SQL Question but you don't use Oracle?

Acknowledgments

OraFAQ Forum Guide History


Re: Forum update [message #506264 is a reply to message #506180] Sat, 07 May 2011 14:07 Go to previous messageGo to next message
BlackSwan
Messages: 26722
Registered: January 2009
Location: SoCal
Senior Member
OraFAQ Forum Guide


Welcome to OraFAQ Forum! Please, read this document before you start to actively participate.

The Posting Guidelines are as follows:

  1. SEARCH both this Forum & GOOGLE BEFORE posting!
  2. Post Operating System (OS) name & version for database (DB) server system
  3. Post Oracle DB version to 4 decimal places (for instance 11.2.0.1).
  4. Choose a topic title that makes sense & clearly states problem to be solved.
    A good title might be "ORA-1555 during pl/sql loop"
    Do NOT use a single word title like "Query", "export", "SQL", etc.
    Do NOT use a two word title like "Slow Query", "Need Help", "Got Error", "SQL Plus", etc.
    A less fortunate choice might be "URGNT PLZ!!!!!!!!!!!!"
    Avoid the following keywords: urgent/please/help/now/immediately (and derivatives)
    Do not post the title or body in UPPER case
  5. Have the courtesy to write in plain English; it is not the first language of most of the participants to this forum,
    but that is no excuse for poor or non-existent punctuation.
  6. Avoid IM-speak; like "U", "Ur", "U r", "Plz", "prb", "qry" especially tend to get on people's nerves.
  7. Do NOT post "procedure does not work", "results are not correct" or similar statement that is devoid of actionable details!
  8. Do NOT describe, explain, report, characterize, portray, expound, paraphrase, or recount what you think happened.
  9. SHOW us using COPY & PASTE the whole session exactly what you do & how Oracle responded as example below
    SQL> set term on echo on
    SQL> @pp.sql
    SQL> DECLARE
      2  STR VARCHAR2(4);
      3  BEGIN
      4  STR := 'FAILS';
      5  END;
      6  /
    DECLARE
    *
    ERROR at line 1:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ORA-06512: at line 4
    

  10. Post FORMATTED code as demonstrated above and detailed in URL below
    http://www.orafaq.com/forum/t/167430/136107/
  11. Post properly INDENTED code as provided by URL below
    http://www.dpriver.com/pp/sqlformat.htm?ref=g_wangz
  12. Provide DDL (CREATE TABLE, etc.) as appropriate instead of listing the table structure.
    It'll help people setting up a test set (yes, some people really do that)
  13. Provide INSERT statements for sample data instead of pasting in or mocking up the results of a SELECT statement.
  14. Provide your expected result set and explain the rules/reasons that lead to it.
  15. Post SQL Client name & version and include OS name & version if different from DB Server.
  16. Forum members are not here to do your work for you nor to do your homework assignment for you.
  17. Don't "wild post", i.e. post a reply that has nothing to do with the original thread.
  18. Choose the appropriate forum. If in doubt, don't worry - moderators can always move it
  19. Don't cross/multi-post. Duplicates will be removed.
  20. Commercial posts are admitted only in the Marketplace Forum.
  21. Do not describe your problem and/or solution in MS Office Word, Excel, *.pdf, *jpg or similar files and attach them to your message.
    Some people can not, some do not want to download them. Plain TXT files are acceptable.
  22. If you found an answer yourself, post it. That way we know the issue is resolved and we might learn from it.

Useful sites

OraFAQ Forum Guide History

[Updated on: Sun, 08 May 2011 13:12]

Report message to a moderator

Re: Forum update [message #506340 is a reply to message #506264] Sun, 08 May 2011 14:13 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8922
Registered: November 2002
Location: California, USA
Senior Member
OraFAQ Forum Guide


Welcome to the OraFAQ forums! Please read and follow these guidelines:


  1. SEARCH both this forum & GOOGLE BEFORE posting!
  2. Post in only one forum. Moderators may move a post to a more appropriate forum. Duplicate posts will be removed.
    Commercial posts are admitted only in the Marketplace Forum.
  3. Choose a topic title that clearly states the problem to be solved. A good title might be "ORA-1555 during pl/sql loop".
    Avoid vague, general, non-specific, titles like "Query", "export", "SQL", etc.
  4. Post your Oracle DB version to 4 decimal places (for instance 11.2.0.1).
  5. Post your Operating System (OS) name & version for your database (DB) server system.
  6. Write a clear explanation of the problem in proper English, with proper grammar and punctuation.
    Do not post in all capitals or use IM-speak like "U", "Ur", "U r", "Plz", "prb", "qry".
    Include all relevant information such as SQL Client name & version and include OS name & version if different from DB Server.
  7. SHOW us using COPY & PASTE from SQL*Plus, the whole session, exactly what you did & how Oracle responded as in the example below.
    Make sure you post some effort of your own. We are not here to do your work or homework for you.
    SQL> set term on echo on
    SQL> @pp.sql
    SQL> DECLARE
      2    STR VARCHAR2(4);
      3  BEGIN
      4    STR := 'FAILS';
      5  END;
      6  /
    DECLARE
    *
    ERROR at line 1:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ORA-06512: at line 4
    

  8. Post FORMATTED code and properly INDENTED code as demonstrated above.
  9. Post TESTED DDL (CREATE TABLE) for referenced tables & INSERT statements for test data to reproduce problem test case.
  10. Provide your expected result set and explain the rules/reasons that lead to it.
  11. Plain text file attachments are acceptable, while Excel, *.pdf, *jpg, or similar files are not.
  12. If you found an answer yourself, post it. That way we know the issue is resolved and we might learn from it.


Useful sites

OraFAQ Forum Guide History




[Updated on: Mon, 09 May 2011 01:58]

Report message to a moderator

Re: Forum update [message #506350 is a reply to message #506340] Sun, 08 May 2011 19:18 Go to previous message
BlackSwan
Messages: 26722
Registered: January 2009
Location: SoCal
Senior Member
consider using one of the shorter sentences below as replacement for longer sentences presently proposed.

  1. Provide DDL (CREATE TABLE, etc.) as appropriate instead of listing the table structure, and INSERT statements for sample data, not just a select or mock-up of the data, sufficient to reproduce the problem. Test it before you post it.
  2. Post TESTED DDL (CREATE TABLE) for referenced tables & INSERT statements for test data to reproduce problem test case.
  3. Post test case (http://www.orafaq.com/wiki/Test_case) when you request code to produce some specific result set.
  4. Provide your expected result set and explain the rules/reasons that lead to it.
  5. Do not describe your problem and/or solution in MS Office Word, Excel, *.pdf, *jpg or similar files and attach them to your message. Some people cannot, some do not want to download them. Plain TXT files are acceptable.
  6. Plain text file attachments are acceptable, while Excel, *.pdf, *jpg, or similar files are not.

[Updated on: Sun, 08 May 2011 19:36]

Report message to a moderator

Previous Topic: backup error on oracle 10
Next Topic: Testing attachments
Goto Forum:
  


Current Time: Wed Jul 15 20:17:15 CDT 2020