https://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf/COMMIT.html Oracle Database issues an implicit COMMIT under the following circumstances: Before any syntactically valid data definition language (DDL) statement, even if the statement results in an error After any data definition language (DDL) statement that completes without an error

It produces 1 row because 'Ninety' is not a number so the first insert failed Even though the first insert failed, it still consumed a number from car_counter (i.e., 1), then Oracle increment the sequence by 10 to 11 for next value. You can change the sequence to INCREMENT BY 9 so that first value is 1, second is 10, but the third is 19. You may START WITH 10 or even 100 if you want things end with 0.

My best guess is that the 2nd column does not have a name. Thus breaking the rules of view creation.

Post it at https://community.oracle.com/tech/developers/categories/sql_developer . That's Oracle's own forum for all things SQL Developer, and Jeff Smith monitors that.

You don't have to click "More" or "Lookup". On the right side, there shows "All" by default, which means all objects will be exported. The image is illustrated as below.

@ != #include @ == START The START command and it's "@" equivalent will invoke a complete, external PL/SQL script. "@" and START are not part of the Oracle PL/SQL syntax, so you can't use it inside other PL/SQL DDL constructs. You should construct either a single script that contains everything or a top-level, "controller" script that includes each of the lower-level elements, in the right order. @ empty_parameter_exception.sql @ insufficient_access_exception.sql @ package_a.sql @ package_a.body.sql @ package_b.sql @ package_b.body.sql Anyway, if your Exceptions, etc., are "standard", then should they not be in their own Package, rather than repeating their [textual] definitions in each, separately-compiled Package?

Looks OK on my 11gXE: SQL> with test (id, name, effdt, node, parent) as 2 (select 'SHA', 'DEPT', date '2001-01-01', 'A10200', 'TOP' from dual union all 3 select 'SHA', 'DEPT', date '2011-01-04', 'A10200', 'X10200' from dual union all 4 select 'SHA', 'DEPT', date '2014-01-01', 'A10200', 'TOP' from dual union all 5 select 'SHA', 'DEPT', date '2014-01-04', 'A10200', 'TOP' from dual 6 ) 7 select id, name, effdt, 8 lag(effdt - 1, 1, null) over (partition by node order by effdt desc) effdtend, 9 node, parent 10 from test 11 order by node, effdt; ID NAME EFFDT EFFDTEND NODE PARENT --- ---- --------- --------- ------ ------ SHA DEPT 01-JAN-01 03-JAN-11 A10200 TOP SHA DEPT 04-JAN-11 31-DEC-13 A10200 X10200 SHA DEPT 01-JAN-14 03-JAN-14 A10200 TOP SHA DEPT 04-JAN-14 A10200 TOP SQL> select * from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production PL/SQL Release 11.2.0.2.0 - Production CORE 11.2.0.2.0 Production TNS for 64-bit Windows: Version 11.2.0.2.0 - Production NLSRTL Version 11.2.0.2.0 - Production SQL>

Something like the following (untested) should work: with partitions as ( select x.*, row_number() over (partition by last_name, first_name, dob order by travel_date desc) as r from my_table as x ) select * from partitions where r = 1;

You can refer to below answer. Issue seems to be at network layer i.e. connection is established but then somehow you are unable to keep that connection alive. Please try this : "mydbmachine.example.com/orclpdb1?expire_time=2" Post

I would separately introduce sorting based on the presence of special characters in HNR, in addition to sorting on the bits related to those characters that you have already implemented. You could try using REGEXP_COUNT for this. Here is how you could go about it: SELECT F.LAG, F.HNR, F.STREET FROM DB.F F ORDER BY F.LAG, F.STREET, TO_NUMBER(regexp_substr(F.HNR, '[[:digit:]]{1,4}')), regexp_count(F.HNR, '[/]'), -- numbers with strokes follow those without strokes regexp_count(F.HNR, '[[:alpha:]]'), -- no-letter numbers first TO_CHAR(regexp_substr(F.HNR, '[[:alpha:]]{1}')), TO_NUMBER(regexp_substr(F.HNR, '[^/]+', 1, 2)); The two additional sorting criteria I added above will result in the following: HNR regexp_count(HNR, '[/]') regexp_count(HNR, '[[:alpha:]]') 48 0 0 48A 0 1 48/1 1 0 As you can see, using them in that specific order will produce the desired sorting order for HNR. See live demo of this solution at SQL Fiddle, at db<>fiddle.

A CASE expression can only return a value, not a fragment of a query. In order to parametrise which column should receive the value passed as an argument, you could try this approach: UPDATE PERSON SET FIRST_NAME = CASE WHEN TARGET_COL = 2 THEN FIRST_NAME ELSE UPDATED_VALUE END, LAST_NAME = CASE WHEN TARGET_COL = 2 THEN UPDATED_VALUE ELSE LAST_NAME END WHERE PERSON_ID = TARGET_ID ; I slightly simplified the logic, because according to your CASE expression, you want to update FIRST_NAME both when TARGET_COL is 1 and when it is anything other than 2. But the second condition actually covers the first one. So we can simplify the logic to this: if TARGET_COL is two, you want to update LAST_NAME, otherwise you want to update FIRST_NAME. So how does the above query work? If TARGET_COL is 2, then FIRST_NAME is updated to FIRST_NAME, i.e. to the same value it already has. This way it remains unchanged. In contrast, LAST_NAME in this case is set to UPDATED_VALUE. If, however, TARGET_COL is not 2 (but e.g. 1), then FIRST_NAME gets UPDATED_VALUE, while LAST_NAME is set to LAST_NAME – in other words, remains unchanged.

This is the SQL statement that SQL Developer generated: CREATE USER "test" IDENTIFIED BY "abc123" ; This makes the username case-sensitive, so the actual username can be used as "test". You tried to login in SQL Developer using the username test. This is not case-sensitive syntax, and it is automatically treated as "TEST", but that user does not exist. Use the case-sensitive syntax for username, so instead of test, provide "test" as username. By the way, we almost never use case-sensitive usernames or object names. You could just create the user without double quotes, and your connection attempt would work: CREATE USER test IDENTIFIED BY "abc123" ; Given that I wanted to connect using a lowercase user name by means of sqlplus, what would I have to enter to connect as "test", for instance? I don't seem to be able to use quotes in the CONNECT clause. " is special character in bash shell, you need to escape it to use it in commandline arguments: sqlplus \"test\"/abc123@mobydick. The connect command handles double quotes just fine: sqlplus /nolog then at SQL> ``` prompt, connect "test"/abc123@mobydick.

AND has precedence over OR. However evaluating the exact order gets complicated, and you cannot guarantee the next person maintaining the code does know the precedence rules. So I always recommend explicitly using parentheses when mixing ANDS and ORS. For your code example, remove the unnecessary parentheses around the individual, and grouped and conditions, and just place a single set of parentheses around the whole group of AND statements - that whole section is only true, if all the conditions are met. Then do your OR Then group the next set of conditions in a single set of parentheses It will be MUCH clearer then. Also looks quite familiar - I work in a hospital too! OK, I've edited as I suggested (Roughly - I'd work on the indentation a little) - bear in mind I can't test it so I might have made a typo. Additional point, using ANSI style joins e.g FROM encounter e JOIN enctr_alias ea ON e.enctr_id = ea.encntr_id instead of joining in the where clause will make this easier to maintain and more flexible as well - is this old code? Oracle PL/SQL: how to get the stack trace, package name and procedure name SELECT /*+ ALL_ROWS */ ENCOUNTER.ENCNTR_ID, ENCNTR_ALIAS.ALIAS, PERSON.NAME_FULL_FORMATTED, CLINICAL_EVENT.EVENT_CD, CV_EVENT.DISPLAY, CLINICAL_EVENT.RESULT_VAL, pi_from_gmt(CLINICAL_EVENT.EVENT_END_DT_TM,( pi_time_zone(1,@Variable('BOUSER')) )) , CE_PRSNL.NAME_FULL_FORMATTED, CV_FACILITY.DISPLAY, CV_NURSE_UNIT.DISPLAY, pi_from_gmt(ENCOUNTER.REG_DT_TM,( pi_time_zone(1,@Variable('BOUSER')) )), pi_from_gmt(ENCOUNTER.ARRIVE_DT_TM,( pi_time_zone(1,@Variable('BOUSER')) )), CV_ROOM.DISPLAY, CV_BED.DISPLAY, trunc((pi_to_gmt(sysdate,( pi_time_zone(2,@Variable('BOUSER')) )) - ( Da2_birth_dttm(PERSON.BIRTH_DT_TM,PERSON.BIRTH_TZ,PERSON.BIRTH_PREC_FLAG,1,0) ))/365.25,0) , ENCOUNTER.REASON_FOR_VISIT, NOMENCLATURE3.SOURCE_IDENTIFIER, NOMENCLATURE3.SOURCE_STRING FROM ENCOUNTER, ENCNTR_ALIAS, CODE_VALUE CV_ENCNTR_ALIAS_TYPE, PERSON, CLINICAL_EVENT, CODE_VALUE CV_EVENT, PRSNL CE_PRSNL, CODE_VALUE CV_FACILITY, CODE_VALUE CV_NURSE_UNIT, CODE_VALUE CV_ROOM, CODE_VALUE CV_BED, DIAGNOSIS, NOMENCLATURE NOMENCLATURE3, PERSON CE_PERSON WHERE --Start of compulsory conditions ( ENCNTR_ALIAS.ENCNTR_ID=ENCOUNTER.ENCNTR_ID AND ENCNTR_ALIAS.ACTIVE_IND = 1 AND ENCNTR_ALIAS.END_EFFECTIVE_DT_TM > SYSDATE AND ENCOUNTER.ACTIVE_IND = 1 AND ENCNTR_ALIAS.ENCNTR_ALIAS_TYPE_CD=CV_ENCNTR_ALIAS_TYPE.CODE_VALUE AND CV_FACILITY.CODE_VALUE=ENCOUNTER.LOC_FACILITY_CD AND ENCOUNTER.ACTIVE_IND = 1 AND ENCOUNTER.LOC_NURSE_UNIT_CD=CV_NURSE_UNIT.CODE_VALUE AND ENCOUNTER.ACTIVE_IND = 1 AND CV_ROOM.CODE_VALUE=ENCOUNTER.LOC_ROOM_CD AND ENCOUNTER.ACTIVE_IND = 1 AND CV_BED.CODE_VALUE=ENCOUNTER.LOC_BED_CD AND ENCOUNTER.ACTIVE_IND = 1 AND DIAGNOSIS.ENCNTR_ID=ENCOUNTER.ENCNTR_ID AND ENCOUNTER.ACTIVE_IND = 1 AND DIAGNOSIS.ACTIVE_IND =1 AND DIAGNOSIS.NOMENCLATURE_ID=NOMENCLATURE3.NOMENCLATURE_ID AND CLINICAL_EVENT.EVENT_CD=CV_EVENT.CODE_VALUE AND ENCOUNTER.ENCNTR_ID=CLINICAL_EVENT.ENCNTR_ID AND ENCOUNTER.ACTIVE_IND = 1 AND ENCOUNTER.PERSON_ID = CLINICAL_EVENT.PERSON_ID AND CLINICAL_EVENT.PERFORMED_PRSNL_ID=CE_PERSON.PERSON_ID AND ENCNTR_ALIAS.ENCNTR_ID=ENCOUNTER.ENCNTR_ID AND CV_ENCNTR_ALIAS_TYPE.CODE_VALUE=ENCNTR_ALIAS.ENCNTR_ALIAS_TYPE_CD AND ENCOUNTER.PERSON_ID=PERSON.PERSON_ID AND DIAGNOSIS.ACTIVE_IND = 1 AND PERSON.ACTIVE_IND = 1 AND ENCNTR_ALIAS.ENCNTR_ID=ENCOUNTER.ENCNTR_ID AND ENCNTR_ALIAS.ACTIVE_IND = 1 AND ENCNTR_ALIAS.END_EFFECTIVE_DT_TM> SYSDATE AND ENCOUNTER.ACTIVE_IND = 1 AND CE_PERSON.PERSON_ID=CE_PRSNL.PERSON_ID AND ENCOUNTER.ACTIVE_IND = 1 AND NOMENCLATURE3.ACTIVE_IND= 1 AND CV_ENCNTR_ALIAS_TYPE.ACTIVE_IND= 1 AND CV_ENCNTR_ALIAS_TYPE.CODE_SET = 319 and CV_ENCNTR_ALIAS_TYPE.CDF_MEANING = 'FIN NBR' and ENCNTR_ALIAS.end_effective_dt_tm> SYSDATE and ENCNTR_ALIAS.active_ind=1 AND CV_FACILITY.CODE_VALUE IN ( 5026 ) -- Look Back 24 hours AND ENCOUNTER.ARRIVE_DT_TM BETWEEN pi_to_gmt(trunc(sysdate-21, 'DAY'), ( pi_time_zone(2,@Variable('BOUSER')) )) AND pi_to_gmt(SYSDATE,( pi_time_zone(2,@Variable('BOUSER')) )) -- AND -- trunc((( pi_from_gmt(ENCOUNTER.REG_DT_TM,( pi_time_zone(1,@Variable('BOUSER')) )) ) - PERSON.BIRTH_DT_TM)/365.25,0) -- >= 74 AND ENCOUNTER.DISCH_DT_TM Is Null ) -- End of compulsory conditions AND CV_EVENT.CODE_VALUE IN (15680255) -- Case #1 All Trach patient OR -----------ALL these need to be met for the data set to qualify ( CV_EVENT.DISPLAY IN ( 'Braden Score' ) AND CLINICAL_EVENT.RESULT_VAL < '14' AND NOMENCLATURE3.SOURCE_IDENTIFIER IN ( '0048084F-1C9E-401C-BBFC-460A9CB4F917','03F9F547-33FA-4938-8BF0-4A8F0F1B69D1','0708636D-9213-4C7A-A226-3E5F71E4647F','208688010','A10673A7-D965-43C4-8B58-9E6174988FC9','AA5E3378-66C0-4317-824F-DD5868512949','C01','C02.0','C02.1','C02.3','C02.8','C02.9','C03.0','C03.1','C03.9','C04.1','C04.9','C05.1','C05.9','C06.0','C06.2','C06.9','C07','C08.0','C08.9','C09.0','C09.8','C09.9','C10.8','C10.9','C11.8','C11.9','C12','C13.1','C13.2','C13.9','C14.0','C15.3','C15.4','C15.5','C15.9','C16.0','C16.1','C16.3','C16.4','C16.9','C17.0','C17.2','C17.9','C18.0','C18.1','C18.2','C18.4','C18.5','C18.6','C18.7','C18.8','C18.9','C19','C20','C21.0','C21.1','C21.8','C22.0','C22.1','C22.2','C22.4','C22.8','C22.9','C23','C24.0','C24.1','C24.8','C24.9','C241771B-DD13-41AC-85CE-63AB8E7B7FC5','C25.0','C25.1','C25.2','C25.4','C25.8','C25.9','C30.0','C31.0','C31.1','C31.2','C31.3','C31.8','C31.9','C32.0','C32.1','C32.2','C32.3','C32.8','C32.9','C34.01','C34.02','C34.10','C34.11','C34.12','C34.2','C34.31','C34.32','C34.90','C34.91','C34.92','C37','C38.1','C40.02','C40.21','C41.0','C41.1','C41.2','C41.3','C41.4','C41.9','C43.10','C43.20','C43.21','C43.30','C43.39','C43.4','C43.52','C43.59','C43.60','C43.61','C43.62','C43.71','C43.72','C43.9', 'C43.9', 'C44.211', 'C44.219', 'Z99.11') AND CLINICAL_EVENT.EVENT_CD IN (839632151, 828777784, 3895375) AND CLINICAL_EVENT.EVENT_CD IN (3797004, 245586366, 82473347, 2165572293) AND CLINICAL_EVENT.RESULT_VAL < '64' ) /* @Variable('UNVNAME') - @Variable('BOUSER') - @Variable('DOCNAME') */ '''

Define "cause a problem"... Will running a query affect the data in any way? No. That is literally what Oracle is designed to do: allow queries and transactions to occur simultaneously. What it might do is affect performance of the system, especially if compute resources are tight. Users could possibly experience a slower response time. That said, your DBA should be able to determine if your actions had any real consequence or risk to your particular system (especially if they're savvy enough to audit your session), or if there is any merit to the CRM's fears.