I dont see that behaviour with the sequence
SQL> select seq.nextval from dual;
NEXTVAL
----------
200013
[wait]
SQL> /
select seq.nextval from dual
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 2336
Session ID: 216 Serial number: 31927
SQL> conn mcdonac/xxxxxx@np12_pooled
Connected.
SQL> select seq.nextval from dual;
NEXTVAL
----------
200014
Are you sure its not just the normal behaviour, ie, that when a sequence is aged out of memory, you lose the cache. In which case, you could pin the sequence with dbms_shared_pool to resolve that.
Re Q2, I'm not sure of the rationale...
conn web[mark]/web@testpdb
makes sense, because 'web' has been given the privilege to connect as mark without mark's password.
conn web[mark/mark]/web@testpdb
says that we already know mark's password, so why wouldn't we just
conn mark/mark@testpdb