Importing Oracle database from dump where source db filesystem has changed
To respond to your comment, all is the default value of content keyword, so you can ignore this one.

Anyway, I have done some tests.
I don't know how is structured your old database, but from your question I note that you want to import only two tablespaces (TAB_ANC, IDX_ANC) and  with all object/schemas within them. If you want to do this, you can perform this kind of import:

impdp system/passwd@HISTO directory=MIG11G dumpfile=20131125_full_HISTO.expdp  parfile=imp_histo.par


The parameter file is this one:

include=schema:"in ('SCHEMA1', 'SCHEMA2', ... , 'SCHEMAn')"
include=tablespace:"in ('TAB_ANC', 'IDX_ANC')"
remap_datafile=/appli2/oradata05/HISTO/HISTO_tab_anc_01.dbf:/appli2/oracle/HISTO/oradata05/HISTO_tab_anc_01.dbf
remap_datafile=/appli2/oradata06/HISTO/HISTO_idx_anc_01.dbf:/appli2/oracle/HISTO/oradata06/HISTO/HISTO_idx_anc_01.dbf


As you can see, you need to include all schemas contained in those tablespaces (or you can also create them from scratch in the new database). To verify these schemas you can run a query like the following:

SELECT username, default_tablespace FROM dba_users;


Remapping datafiles is useful when you move databases between platforms that have different file naming conventions.

I think you can use remap_tablespace when you have already created (manually) all the required tablespace in the target database, but with different names.